Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Unable to remote debug XP Home machine

1 view
Skip to first unread message

Simon Bond

unread,
Aug 27, 2003, 11:06:25 AM8/27/03
to
Running VS.NET 2003 on Win2k3 server, I have an XP home machine on the
network running msvcmon (installed via vsnet setup cd) which is able to
share files with my dev win2k3 machine and is otherwise networked fine.

Docs say that you have to use TCP/IP for XP Home, so i selected TCP/IP for
transport, type in \\192.168.0.17 (ip of the xp home machine) and I get the
following error:

"Unable to connect to '\\192.168.0.17'. The IP address for the remote
machine is not valid."

The XP Home machine is running: "msvcmon.exe -tcpip -anyuser", so it should
be listening correctly.

Any help appreciated.

- Simon.

Chris Cook

unread,
Aug 27, 2003, 2:28:08 PM8/27/03
to

Try typing in just "192.168.0.17" without the "\\". (The "\\" is used to
indicate to Windows that you are about to specify a machine name or address
when referring to a Windows network share -- it's not actually part of the
IP address.)

Chris

--------------------
>From: "Simon Bond" <simon_...@asp-x.net>
>Subject: Unable to remote debug XP Home machine
>Date: Wed, 27 Aug 2003 12:06:25 -0300
>Lines: 20
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.3790.0
>X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Message-ID: <uu3TKzKb...@tk2msftngp13.phx.gbl>
>Newsgroups: microsoft.public.vsnet.debugging
>NNTP-Posting-Host: hlfx3-1334.ns.aliant.net 156.34.85.54
>Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
>Xref: cpmsftngxa06.phx.gbl microsoft.public.vsnet.debugging:3174
>X-Tomcat-NG: microsoft.public.vsnet.debugging


--

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.

Simon Bond

unread,
Aug 28, 2003, 7:49:49 AM8/28/03
to
Good call, Chris. That did the trick--cheers!

- Si.


"Chris Cook" <cc...@microsoft.com> wrote in message
news:x05g9jMb...@cpmsftngxa06.phx.gbl...

diop

unread,
Dec 16, 2004, 9:46:54 PM12/16/04
to
I get the same error message. I tried using \\192.168.21.12 and
192.168.21.12. I also used the machine name.
I am using TCP/IP to connect, but I also tried in pipe mode. Thanks for
any help.

diop

unread,
Dec 16, 2004, 9:46:42 PM12/16/04
to
I get the same error message. I tried using \\192.168.21.12 and
192.168.21.12. I also used the machine name.
I am using TCP/IP to connect, but I also tried in pipe mode. Thanks for
any help.
0 new messages