Can't remote desktop/ping XP PC, but can access its share folders

My home network:

• Windows 7 PC
• Windows XP Laptop
• Both cable connected to a TalkTalk router with Firewall
• Neither PC has a software firewall enabled

I haven't used the laptop for 6 months. I used to be able to do everything I discuss below, the only change in the past 6 months is I have re-installed Windows 7 onto a new SSD.

Yesterday

So, yesterday, from my Windows 7 PC, I:

Could successfully:

• Remote desktop into the XP PC within my home network
• Ping it using CMD using the XP PC name AND its internal IP address

Could NOT:

• See the XP PC on my Windows 7 network map
• Access it's shares

I then noticed "File and Printer Sharing for Microsoft Networks" was off on the XP's network adapter. As soon as I turned it on, from my Windows 7 PC, I could successfully:

• See it on my Windows 7 network map
• Access it's shares

However, since then, the XP machine has installed a lot of updates. I don’t know what – there were so many I just didn’t check.

Today

Now I find I cannot:

• Remote desktop into the XP PC (it says it cannot find the laptop – the PC name I'm using definitely matches the name as per the "Remote" (desktop) tab on the laptop).
• Ping it using CMD using the PC name OR its internal IP address

Can anyone help me to remote desktop into the XP PC again?

Thanks in advance,
Rave

Firstly, thanks for the reply.

2xg said:

If you can't ping the XP PC, I'd look on any Security or Firewall Software installed.

Neither PC has a software firewall enabled

2xg said:

Can you also provide an ipconfig /all of the XP computer? Here's a Tutorial.

Here they are:

Windows IP Configuration
Host Name . . . . . . . . . . . . : DRM-Evo-Laptop
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : dlink.com


Ethernet adapter Hamachi:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hamachi Network Interface
Physical Address. . . . . . . . . : 00-23-C3-46-F7-31
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : No
IP Address. . . . . . . . . . . . : 5.70.247.49
Subnet Mask . . . . . . . . . . . : 255.0.0.0
IP Address. . . . . . . . . . . . : fe80::223:c3ff:fe46:f731%4
Default Gateway . . . . . . . . . :
DHCP Server . . . . . . . . . . . : 5.0.0.1
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%2
fec0:0:0:ffff::2%2
fec0:0:0:ffff::3%2
Lease Obtained. . . . . . . . . . : 05 January 1980 01:08:08
Lease Expires . . . . . . . . . . : 04 January 1981 01:08:08


Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : dlink.com
Description . . . . . . . . . . . : Intel(R) PRO/100 VM Network Connection
Physical Address. . . . . . . . . : 00-02-A5-B4-52-C9
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.5
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : fe80::202:a5ff:feb4:52c9%5
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
Lease Obtained. . . . . . . . . . : 05 January 1980 01:05:56
Lease Expires . . . . . . . . . . : 06 January 1980 01:05:56


Tunnel adapter Teredo Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : FF-FF-FF-FF-FF-FF-FF-FF
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::ffff:ffff:fffd%6
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled


Tunnel adapter 6to4 Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 6to4 Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 05-46-F7-31
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 2002:546:f731::546:f731
Default Gateway . . . . . . . . . : 2002:c058:6301::c058:6301
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%2
fec0:0:0:ffff::2%2
fec0:0:0:ffff::3%2
NetBIOS over Tcpip. . . . . . . . : Disabled


Tunnel adapter Automatic Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Automatic Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 05-46-F7-31
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::5efe:5.70.247.49%2
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%2
fec0:0:0:ffff::2%2
fec0:0:0:ffff::3%2
NetBIOS over Tcpip. . . . . . . . : Disabled


Tunnel adapter Automatic Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . : dlink.com
Description . . . . . . . . . . . : Automatic Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : C0-A8-01-05
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::5efe:192.168.1.5%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

2xg said:

Thanks for the output, see if temp disabling Himachi helps. Disable it from your computer's Device Manager.

Thanks for the reply.

I actually disabled it yesterday but its enabled itself again.

Anyway, I tried disabling it but that didn't work. Then tried uninstalling (the adapter from Device Manager) - didn't think that would make any difference and I was right!

I tried RD and pinging the PC name and its IP.

I have no idea if this is related, but the laptop is setup to act as a web server. We use DynDNS so our domain responds. However, that's not working either.

XP PC

COM+ Event System (for WZC issues)

• Started | Manual
• x1 'depends on', which is Started | Automatic

Computer Browser

• I could not find this in the Services list.

DHCP Client

• Started | Automatic
• x3 'depends on':
  
  • AFD Networking Support Environment: I could not find in the Services list.
  • IPSEC is mentioned. IPSEC is set to start automatically but its not started and won't start. I get the same error as this: Event ID:7023 IPSec Service unable to start at boot. - Geeks to Go Forums ...should I look into resolving this? is it required?
  
  

DNS Client

• Started | Automatic
• x1 'depends on': IPSEC is mentioned. See above.

Network Connections

• Started | Manual
• x1 'depends on', which is Started | Automatic

Network Location Awareness

• Started | Manual
• x2 'depends on':
  
  • AFD Networking Support Environment See above.
  • IPSEC is mentioned. See above.
  
  

Remote Procedure Call (RPC)

• Started | Automatic
• No 'depends on'.

Server

• Started | Automatic
• No 'depends on'.

TCP/IP Netbios helper

• I have a feeling this was not started but set to automatic - not 100%. Anyway, after starting it did not resolve the issue.
• x2 'depends on':
  
  • AFD Networking Support Environment See above.
  • IPSEC is mentioned. See above.
  
  

WLAN AutoConfig (for Vista and Windows 7 only)
NA

Workstation
I could not find this on XP.

Win7 PC
I also applied all of these to Windows 7. I checked the 'depends on' Services for each. All were started. WLAN AutoConfig was disabled but even after starting it, it did not resolve the issue.

I will try Secunia on both over the weekend but thought I would update.

Thanks once again for your help - it is really appreciated.

Have a good weekend.

Have you tried pinging the desktop from the XP machine? Can you ping the router from the XP machine?

Win7 network map - possibly related: XP Computers in the Windows 7 Network Map

I've cracked it...a big thanks to everyone who replied.

xBungler said:

Have you tried pinging the desktop from the XP machine? Can you ping the router from the XP machine?

Everything pinged fine.

xBungler said:

Win7 network map - possibly related: XP Computers in the Windows 7 Network Map

When I tried that, it wouldn't install on my XP SP3 machine. The article says its for SP2.

After coming across this link:
Link Layer Topology Discovery (LLTD) protocol In SP3

This blog suggests a method to get Link Layer Topology Discovery (KB922120) working on SP3:
Link Layer Topology Discovery (KB922120) not included in SP3 no problem!!! Read on… « x3webworx no sugar coating blog

I now see the XP machine on the Win7's network map.

I can remote desktop to it, but ONLY by using the XPs IP address - not the computer name, which worked previously.

2xg said:

Also, please install and run Secunia PSI and let us know if there are any vulnerable outdated programs installed in your computer bec. that might be causing some issues.

This didn't resolve this particular issue bit it was a good recommendation. I've installed it on all my machines and I've added it to my list for all future installations I do.

Thanks again everyone - big thumbs up to this forum.