IP Addressing Correct?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am trying to set up remote desktop connections on my WIN XP Pro Home
Computer. My remote Laptop is running XP Home. When setting up the network
the "Home Computer" can ping the "Laptop's" static IP address but not it's
own static IP adrress. When it pings it's own address it generates "mesage
timed out" error's. The Ethernet adpater is working fine as I can easily
reconfigure it for DHCP and successfully access the internet. The fact that
I can ping 1 of the 2 address suggests the cross over cable is fine. Can
anyone point me in the right direction?
 
it could be the firewall blocking the ping. post the result of ipconfig /all may help.

Bob Lin, MS-MVP, MCSE & CNE
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.
Don't send e-mail or reply to me except you need consulting services. Posting on MS newsgroup will benefit all readers and you may get more help.
I am trying to set up remote desktop connections on my WIN XP Pro Home
Computer. My remote Laptop is running XP Home. When setting up the network
the "Home Computer" can ping the "Laptop's" static IP address but not it's
own static IP adrress. When it pings it's own address it generates "mesage
timed out" error's. The Ethernet adpater is working fine as I can easily
reconfigure it for DHCP and successfully access the internet. The fact that
I can ping 1 of the 2 address suggests the cross over cable is fine. Can
anyone point me in the right direction?
 
I am trying to set up remote desktop connections on my WIN XP Pro Home
Computer. My remote Laptop is running XP Home. When setting up the network
the "Home Computer" can ping the "Laptop's" static IP address but not it's
own static IP adrress. When it pings it's own address it generates "mesage
timed out" error's. The Ethernet adpater is working fine as I can easily
reconfigure it for DHCP and successfully access the internet. The fact that
I can ping 1 of the 2 address suggests the cross over cable is fine. Can
anyone point me in the right direction?
Click to expand...

If a computer can ping another computer, but not itself, and gets "time out",
it's usually either an LSP / Winsock problem, or a firewall problem.

Check for corrupt LSP / Winsock problem.
<http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>

Look for any misconfigured or overlooked firewalls. What antivirus products do
you use?
<http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>\

--
Cheers,
Chuck MS-MVP [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.
 
Back
Top