Can't connect XP pc to Win 7

[pilotbob]

I have 5 PC's connected by LAN at my workplace 4 have Win 7 Pro 64 the other has XP Pro. All has worked perfectly for months however I've had to upgrade the "Master" so have re-installed everything and give the new PC the same identity as the old one. Without any issues all the Win 7 machines talk to each other but the XP machine wont. I can see the XP machine on the network from all the Win 7 machines and can see all the Win 7 machines on the XP one but when I try to access from either direction I get a "Windows cannot access" message and troubleshooter can't resolve it. I can't understand why it used to be ok but not anymore. To save me from pulling out what hair I have left, any ideas?

Just to add network name "Workgroup" is the same on all and location is "Work"

Bob.

 

[TerryNet]

... upgrade the "Master" ...

What is this "Master", what upgrade, and what, if any, changes did the upgrade make to the LAN?

For the XP and one of the Windows 7 PCs (if you don't understand the "pings" just skip them now and we can get them later) ...

Open a (black) Command Prompt window:
Hold the Windows logo key and press r; in the Run box type cmd and click on OK.

Type the following commands:

IPCONFIG /ALL

[Note that there is no space between the slash and ALL.]

ping <the other PC by name>

ping <the other PC by IP address>
[Press ENTER after each command.]

Right click in the command window and choose Select All, then hit Enter.
Paste the results in a message here.

If necessary use a text file and removable media to copy the results to a computer with internet access.

 

[pilotbob]

Thanks for the reply, sorry if I've introduced confusion but Master refs to the Main PC on the network, all user files are stored here. The upgrade was simply a better processor/mb and disk drive etc. No changes to the lan.

Not sure what has happened but after trying multiple times this morning and re-booting both machines a number of times without success, it looks like it's all working properly????? Maybe the reports below will confirm this. Networking has always been for me a bit of a nightmare and seems ridiculously complicated. Anyway whatever you can glean from this and tell me would be appreciated. Thanks again.

Results for XP PC,

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Bob>ipcofig /all
'ipcofig' is not recognized as an internal or external command,
operable program or batch file.

C:\Documents and Settings\Bob>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : CNC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe FE Family Controller
Physical Address. . . . . . . . . : 00-1E-90-79-9D-8A
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.5
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : 15 April 2015 09:31:06
Lease Expires . . . . . . . . . . : 16 April 2015 09:31:06

C:\Documents and Settings\Bob>ping Bob-pc

Pinging Bob-pc [192.168.0.13] with 32 bytes of data:

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

Ping statistics for 192.168.0.13:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Documents and Settings\Bob>


Results for Win 7 PC,

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>ipcofig /all
'ipcofig' is not recognized as an internal or external command,
operable program or batch file.

C:\Windows\system32>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : Bob-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : BC-5F-F4-F3-2E-F4
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::a0ac:f410:47ca:f9a0%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.13(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 15 April 2015 13:31:45
Lease Expires . . . . . . . . . . : 16 April 2015 13:31:46
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DHCPv6 IAID . . . . . . . . . . . : 247226356
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1C-66-54-77-BC-5F-F4-F3-2E-F4

DNS Servers . . . . . . . . . . . : 192.168.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{904D2AAF-8FA8-483B-9B54-4F0C8AB592E4}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:9d38:6abd:3c6f:1a3a:aee0:9909(Pref
erred)
Link-local IPv6 Address . . . . . : fe80::3c6f:1a3a:aee0:9909%13(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled

C:\Windows\system32>ping CNC

Pinging CNC [192.168.0.5] with 32 bytes of data:
Reply from 192.168.0.5: bytes=32 time<1ms TTL=128
Reply from 192.168.0.5: bytes=32 time<1ms TTL=128
Reply from 192.168.0.5: bytes=32 time<1ms TTL=128
Reply from 192.168.0.5: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.0.5:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Windows\system32>

 

[TerryNet]

You're welcome.

Anyway whatever you can glean from this and tell me would be appreciated.

Mainly that it takes you two tries to type "ipconfig"!
Actually the pings confirm that things are, or should be, working. It's possible that before it started working that a ping would have failed, and that may have given us a clue as to why.

Taking the one computer offline to make the hardware changes is technically a change to the network and then reconnecting it to the LAN is another change. These aren't the kind of changes I was asking about, but they can cause some temporary disruption because after any such (even minor) change the Computer Browser service can take up to 20 minutes or even longer to get all devices up to date with the names/addresses of the other devices on the network. While I don't have hard data on this I think that XP is much, much more susceptible to this delay than is Windows 7.

So, 20 minutes or even 40 minutes of incomplete access can be explained by the Computer Browser service. I have no clue about anything longer than that. Whenever I run into this I just use IP address access--e.g., to access the XP machine type \\192.168.0.5 into a Run box.