Vista cannot find XP computer located on the same switch, HELP!

P

Pete

Hi:

I have XP Pro on a desktop and Vista 64 Home on my laptop. They both are
connected by ethernet to the same switch. Both computer belong to the same
workgroup. Vista can find just about every computer on campus except my XP
box. The XP machine can find all the workgroup computers except for my
Vista laptop. Both systems are uptodate with plethoria of windows updates,
so can someone explain why they cannot find each other when they the are
about 1 foot apart. I dont believe it is a firewall problem because they
can each find all the other computers on the network including computers in
the same workgroup.

XP networking has always been horrible and in many cases you could search
for a computer by name that did not appear and XP would find it. Vista
seems to have lost this handy capability and the networking is much worse.
For example, even if you only are interested in computers in your workgroup
it searches all the computers and just filters them. It also seems to
forget where the computers are located each time and sometime it will find a
computer and other times not.

Any help would be much appreciated.

TIA,

Pete
 
P

Pete

Good ideas, first from Vista

Pinging 132.235.23.132 with 32 bytes of data:

Reply from 132.235.23.132: bytes=32 time=1ms TTL=128

Reply from 132.235.23.132: bytes=32 time=2ms TTL=128

Reply from 132.235.23.132: bytes=32 time<1ms TTL=128

Reply from 132.235.23.132: bytes=32 time<1ms TTL=128

Ping statistics for 132.235.23.132:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 2ms, Average = 0ms

Windows IP Configuration

Host Name . . . . . . . . . . . . : Harring0
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : cns.ohiou.edu

Wireless LAN adapter Wireless Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Dell Wireless 1505 Draft 802.11n WLAN
Mini-Card
Physical Address. . . . . . . . . : 00-23-4D-95-BE-51
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : cns.ohiou.edu
Description . . . . . . . . . . . : Marvell Yukon 88E8040 PCI-E Fast
Ethernet Controller
Physical Address. . . . . . . . . : 00-21-9B-F6-77-AB
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . :
fe80::b006:4049:e713:9145%11(Preferred)
IPv4 Address. . . . . . . . . . . : 132.235.26.86(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.252.0
Lease Obtained. . . . . . . . . . : Friday, December 19, 2008 3:06:17 AM
Lease Expires . . . . . . . . . . : Friday, December 19, 2008 8:06:16 PM
Default Gateway . . . . . . . . . : 132.235.27.254
DHCP Server . . . . . . . . . . . : 132.235.51.124
DNS Servers . . . . . . . . . . . : 132.235.64.1
132.235.64.2
Primary WINS Server . . . . . . . : 132.235.8.198
Secondary WINS Server . . . . . . : 132.235.197.38
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 6:

Connection-specific DNS Suffix . : cns.ohiou.edu
Description . . . . . . . . . . . : 6TO4 Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2002:84eb:1a56::84eb:1a56(Preferred)
Default Gateway . . . . . . . . . : 2002:c058:6301::c058:6301
DNS Servers . . . . . . . . . . . : 132.235.64.1
132.235.64.2
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 7:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . :
2001:0:4137:9e50:30d9:526:7b14:e5a9(Preferred)
Link-local IPv6 Address . . . . . :
fe80::30d9:526:7b14:e5a9%10(Preferred)
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 11:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :
isatap.{9D28E948-5E08-48E7-9A2D-F581653341FB}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 12:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : cns.ohiou.edu
Description . . . . . . . . . . . : isatap.cns.ohiou.edu
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Pete
 
P

Peter de B. Harrington

Now XP

Pinging 132.235.26.86 with 32 bytes of data:



Request timed out.

Request timed out.

Request timed out.

Request timed out.



Ping statistics for 132.235.26.86:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

I can see that the IP number looks bad, but it is in the Vista IP config???

Windows IP Configuration



Host Name . . . . . . . . . . . . : harring10

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No



Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : NVIDIA nForce Networking
Controller

Physical Address. . . . . . . . . : 00-01-29-27-E5-95

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 132.235.23.132

Subnet Mask . . . . . . . . . . . : 255.255.0.0

IP Address. . . . . . . . . . . . : fe80::201:29ff:fe27:e595%6

Default Gateway . . . . . . . . . : 132.235.23.254

DNS Servers . . . . . . . . . . . : 132.235.64.1

132.235.64.2

fec0:0:0:ffff::1%1

fec0:0:0:ffff::2%1

fec0:0:0:ffff::3%1



Tunnel adapter Teredo Tunneling Pseudo-Interface:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Teredo Tunneling
Pseudo-Interface

Physical Address. . . . . . . . . : 80-00-FB-22-7B-14-E8-7B

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : fe80::ffff:ffff:fffd%4

Default Gateway . . . . . . . . . :

NetBIOS over Tcpip. . . . . . . . : Disabled



Tunnel adapter 6to4 Tunneling Pseudo-Interface:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : 6to4 Tunneling Pseudo-Interface

Physical Address. . . . . . . . . : 84-EB-17-84

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 2002:84eb:1784::84eb:1784

Default Gateway . . . . . . . . . : 2002:c058:6301::c058:6301

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1

fec0:0:0:ffff::2%1

fec0:0:0:ffff::3%1

NetBIOS over Tcpip. . . . . . . . : Disabled



Tunnel adapter Automatic Tunneling Pseudo-Interface:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Automatic Tunneling
Pseudo-Interface

Physical Address. . . . . . . . . : 84-EB-17-84

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : fe80::5efe:132.235.23.132%2

Default Gateway . . . . . . . . . :

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1

fec0:0:0:ffff::2%1

fec0:0:0:ffff::3%1

NetBIOS over Tcpip. . . . . . . . : Disabled

TIA,

Pete
 
R

Robert L. \(MS-MVP\)

This is confused configuration. Do you use public IP addresses? Basically,
the problem are both computer are not in the same subnet and using different
default gateway.

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
 
P

Peter de B. Harrington

Pete said:
Good ideas, first from Vista

Pinging 132.235.23.132 with 32 bytes of data:

Reply from 132.235.23.132: bytes=32 time=1ms TTL=128

Reply from 132.235.23.132: bytes=32 time=2ms TTL=128

Reply from 132.235.23.132: bytes=32 time<1ms TTL=128

Reply from 132.235.23.132: bytes=32 time<1ms TTL=128

Ping statistics for 132.235.23.132:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 2ms, Average = 0ms

Windows IP Configuration

Host Name . . . . . . . . . . . . : Harring0
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : cns.ohiou.edu

Wireless LAN adapter Wireless Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Dell Wireless 1505 Draft 802.11n
WLAN Mini-Card
Physical Address. . . . . . . . . : 00-23-4D-95-BE-51
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : cns.ohiou.edu
Description . . . . . . . . . . . : Marvell Yukon 88E8040 PCI-E Fast
Ethernet Controller
Physical Address. . . . . . . . . : 00-21-9B-F6-77-AB
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . :
fe80::b006:4049:e713:9145%11(Preferred)
IPv4 Address. . . . . . . . . . . : 132.235.26.86(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.252.0
Lease Obtained. . . . . . . . . . : Friday, December 19, 2008 3:06:17 AM
Lease Expires . . . . . . . . . . : Friday, December 19, 2008 8:06:16 PM
Default Gateway . . . . . . . . . : 132.235.27.254
DHCP Server . . . . . . . . . . . : 132.235.51.124
DNS Servers . . . . . . . . . . . : 132.235.64.1
132.235.64.2
Primary WINS Server . . . . . . . : 132.235.8.198
Secondary WINS Server . . . . . . : 132.235.197.38
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 6:

Connection-specific DNS Suffix . : cns.ohiou.edu
Description . . . . . . . . . . . : 6TO4 Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2002:84eb:1a56::84eb:1a56(Preferred)
Default Gateway . . . . . . . . . : 2002:c058:6301::c058:6301
DNS Servers . . . . . . . . . . . : 132.235.64.1
132.235.64.2
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 7:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . :
2001:0:4137:9e50:30d9:526:7b14:e5a9(Preferred)
Link-local IPv6 Address . . . . . :
fe80::30d9:526:7b14:e5a9%10(Preferred)
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 11:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . :
isatap.{9D28E948-5E08-48E7-9A2D-F581653341FB}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 12:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : cns.ohiou.edu
Description . . . . . . . . . . . : isatap.cns.ohiou.edu
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Pete
Click to expand...
Happy 2009!!!

I spent yesterday afternoon working on this problem. I found that the
firewall on the vista machine was preventing the Ping from being returned so
that was fixed.

I found on the XP machine that the LLTD protocol was not present although
SP3 was. I tried install the LLTD, which does not install if SP3 is present.
I tried the hotfix which installed, but did not stay. Each time exited the
connection properties and re-entered it would be gone.

SO

I uninstalled SP3 and reinstalled SP3 and all the security updates. The
system seems to back to normal and the LLTD protocol was present and
installed properly. However, the XP computer can still not see the VISTA
machine and vice versa. The network capabilities of VISTA are just as bad as
Windows XP, it takes too long for the Windoze to find computers on the
network. I would imagine even a monkey would have added some backwards
compatability for previous versions of the OS because most networks might
have older systems on it.

Anyway, I have no ideas of what to try next. Any suggestions would be
appreciated. I will add the new ipconfig/all files as replies to this
message.

Best wishes for 2009,

Pete

PS If you want to buy a notebook, don't buy a vista system. Get an Apple so
you wont have these frustrations.
 
P

Peter de B. Harrington

Hi:

I am making progress. Computers are in the network map, but not in the list.

I have a new problem in that the network printer appears in the network map,
Vista can't connect to it and it too does not appear in the network list,
but I can remote desktop to the ip address. I am on a campus network. I
think VISTA just cannot deal with the large numbers of computers on the WAN.

Any clues to make this horrid operating system work.

Best wishes,

Pete
 
P

Pete

Hi All:

Here is a list of steps that were required to get my new VISTA Premium Home
Laptop to work on our existing network populated with XP Pro boxes. It is a
university network. I am skipping the obvious steps because this advice is
spread all over the web like:
1. Make sure all the computers are connected
2. Make sure the router is turned on
3. Make sure the workgroups are the same on all the computers
4. Make sure all systems are uptodate

1. Getting LLTD to install when it is missing from XP SP3. Cannot install
after SP3 is downloaded unless manually copied into the directories. The MS
hotfix fails to install properly either. You can install the LLTD protocol
in the TCP/IP properties, but it will be gone the next time you enter the
properties. No error message is ever given by XP.

On the XP Machines where LLTD is uninstallable

A. Save the LLTD update WindowsXP-KB922120-v5-x86-ENU.exe to your hard disk.
A good location is C:\
B. Enter the command prompt and unpack it by entering
C:\WindowsXP-KB922120-v5-x86-ENU.exe -xC:\WindowsXP-KB922120-v5-x86-ENU
C. Copy the following files to these locations
1. C:\WindowsXP-KB922120-v5-x86-ENU\SP2QFE\rspndr.sys ->
C:\windows\system32\drivers
2. C:\WindowsXP-KB922120-v5-x86-ENU\SP2QFE\rspndr.exe ->
C:\windows\system32\
3. C:\WindowsXP-KB922120-v5-x86-ENU\SP2QFE\rspndr.inf -> C:\windows\inf
4. Reboot
5. Install the LLTD protocol in the TCP/IP properties and verify that it is
there after exiting the properties.
If all is successful you will now see the computers on the network map.

If not, you can try to uninstall SP3 and reinstalling all the security
updates (will take a couple of hours so avoid this step if you can).

Machines are still invisible
Go into the TCP/IP properties and ensure that
1. subnet mask is set to 255.255.255.0 and not 255.255.0.0 that windoze
picks as a default
2. advanced->wins check enable NetBios over TCP/IP
3. The networking in Vista is much less efficient than XP/Pro so if your
computers are on different subnets, it times out for large networks. This
presents a problem if some computers use static and others use dynamic ip. I
had to set the Vista notebook to a static ip, so it was on the same subnet
as the other network computers. This was not the case for the laptop that
had XP Pro which this system is replacing. There are many other missing
network capabilities of Vista as well, such as having a workgroup folder
that you could drag onto your desktop.

Getting vista recognize a plugnplay printer on an XP Pro box.
1. Forget about adding the printer driver through the network. Vista cannot
do this, while XP Pro could. Instead connect the printer directly to the
vista box, let the printer be recognized and install the printer driver.
2. Now hook your computer back to the network and the printer back to the XP
host.
2. Go to printer in the control panel
3. Add a printer
4. Add a local printer (counter intuitive but it works)
5. Create a new port, pick local port
6. Type \\computer name\printer name (before trying this be sure that the
computer is listed in the network list and when you open it you see the
printer) use the names of the printer and computer just as they appear in
the network list.

This troubleshooting required 2 full work days, so much for MS misleading
ads about enhancing office productivity. I am not satisfied that the laptop
had to be switched from dynamic ip to static ip to network effectively, so
Vista is much worse on the large networks that you find at most
universities. Hope that I can save you some time and frustrations in 2009.

Happy Computing!!!

Pete
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Vista Laptop cannot find XP Computer on Wireless Network 3
Please Help: Network XP Pro SP2 & Vista HP Computers 4
Vista / XP workgroup networking 8
Vista computer does not discover XP computers 3
Cannot access xp computer on network 6
File Sharing with an XP laptop and Vista laptop on the same networ 7
Adding Vista computer to XP workgroup 1
Cannot get XP desktop-Vista laptop network to work 5

Top