Re: Remote debugging broken on WinXP Pro SP2
- From: Chuck Chopp <ChuckChopp@xxxxxxxxxxx>
- Date: Tue, 28 Mar 2006 20:34:19 -0700
Never mind... I figured it out.
I found that the WinXP Pro SP2 VM had some SSL-based VPN client software from Juniper Networks installed on it that was interfering with MSVCMON. Juniper Networks' "Network Connect" and "Secure Application Manager [w/LSP]" are apparently incompatible with MSVCMON in native TCP/IP mode. I was able to determine that this VM was used to access a customer's private network via the Juniper Networks VPN clients sometime in the past month or so and that's when & how the VPN client software was installed. I had forgotten that it was there, but a review of the installed applications showed it present on the WinXP Pro SP2 VM but not on the Win2K3 SP1 VM.
Has anybody else encountered any similar problems with these VPN clients interfering with debugging?
--
Chuck Chopp
ChuckChopp (at) rtfmcsi (dot) com http://www.rtfmcsi.com
RTFM Consulting Services Inc. 864 801 2795 voice & voicemail
103 Autumn Hill Road 864 801 2774 fax
Greer, SC 29651
"Racing to save lives"
The Leukemia & Lymphoma Society - Team in Training
http://www.active.com/donate/tntsc/tntscCChopp
Do not send me unsolicited commercial email.
.
- References:
- Remote debugging broken on WinXP Pro SP2
- From: Chuck Chopp
- Remote debugging broken on WinXP Pro SP2
- Prev by Date: Remote debugging broken on WinXP Pro SP2
- Next by Date: Linking options for debugging
- Previous by thread: Remote debugging broken on WinXP Pro SP2
- Next by thread: Linking options for debugging
- Index(es):
Relevant Pages
|
