|
|
Welcome to Vista Banter. You are currently viewing our boards as a guest which gives you limited access to view most discussions, articles and access our other FREE features. By joining our free community you will have access to ask questions and reply to others posts, upload your own photos and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact support. |
|
|||||||
| Networking with Windows Vista Networking issues and questions with Windows Vista. (microsoft.public.windows.vista.networking_sharing) |
|
|
LinkBack | Thread Tools | Display Modes |
November 6th 08, 06:19 PM
posted to microsoft.public.windows.vista.networking_sharing
|
|||
|
|||
Now pinging isn't ever right XP to Vista
I have XP machines on a home network where all the networking is OK. I'm
having such a variety of problems with the Vista on the network though. I have XP machines at IP addresses 192.168.1.50 (static) and 192.168.1.103 (current dynamic) they can ping back and forth and can ping my Vista at 1092.168.1.102 (current dynamic). But when I ping the XP machines from the Vista it times out. This, I think, is new behavior even though I haven't changed things recently. If I ping an XP to another XP by name it works. If I ping an XP from the Vista by name it tries to ping 207.69.131.10 this behavior has been around forever. The Vista is configured to be on a private network and to allow file sharing. Amy ideas? Thanks, Chas 
|
|
November 7th 08, 12:51 AM
posted to microsoft.public.windows.vista.networking_sharing
|
|||
|
|||
|
Now pinging isn't ever right XP to Vista
We have a TCP/IP settings issue here. Posting the result of ipconfig /all on
Vista may help. Also you may want to check this search result. troubleshooting ping issues Ping lists a public IP instead of private IP. Symptom: when you ping a LAN computer like ping chicagotechpc1, you may receive a public ip 64.176.153.103 ... www.chicagotech.net/troubleshootingping.htm -- 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 "chasgl" wrote in message ... I have XP machines on a home network where all the networking is OK. I'm having such a variety of problems with the Vista on the network though. I have XP machines at IP addresses 192.168.1.50 (static) and 192.168.1.103 (current dynamic) they can ping back and forth and can ping my Vista at 1092.168.1.102 (current dynamic). But when I ping the XP machines from the Vista it times out. This, I think, is new behavior even though I haven't changed things recently. If I ping an XP to another XP by name it works. If I ping an XP from the Vista by name it tries to ping 207.69.131.10 this behavior has been around forever. The Vista is configured to be on a private network and to allow file sharing. Amy ideas? Thanks, Chas
|
|
November 7th 08, 08:34 PM
posted to microsoft.public.windows.vista.networking_sharing
|
|||
|
|||
|
Now pinging isn't ever right XP to Vista
Many of my problems went away when I got my NOrton Firewall configured to
allow access. The pinging by IP address works now. But pinging from the VIsta by name still doesn't work. When I followed you link I found the entry Troubleshooting Ping Can't ping another computer because of the ICF Can't use ping Can't ping outside IP or name Error code 65, 10043, 10050 and 10091 transmit failed Destination not unreachable Hardware Error Host is unreachable Pinging host name display FQDN Ping lists a public IP instead of private IP Receiving a reply from a different IP TTL expired in transit Can't ping another computer because of the ICF Sometimes, XP's built-in Firewall may enable after running network setup wizard on LAN connections. You can't ping or access the XP computer. To disable the XP firewall on the connection, go to the properties of the Connections, select Advanced, and deselect the firewall. Can't ping outside IP or name If you can't ping outside IP, make sure you have correct gateway. If you can't ping outside computer name or web name, check the DNS settings. Can't use ping If you cannot use ping successfully at any point, confirm that: 1)The computer was restarted after TCP/IP was configured. 2) The IP address of the local computer is valid and appears correctly on ipconfig /all. 3) IP routing is enabled and the link between routers is operational. 4) For the security reasons, many organizations block the return of ICMP (ping) packets so that ping or tracert may not be possible to obtain a response. Error code 65, 10043 and 10050, transmit failed Symptoms: When using ping command, you may receive either of the following: "Transmit failed, error code 65" or "Transmit failed, error code 10050" Resolutions: make sure your firewall, NAT or router doesn't disable ping and to allow ICMP Echo and Echo Reply packets. Hardware Error Symptom: when you try to ping an IP, you may receive "hardware error" reply. Causes: 1. Bad NIC. 2. The cable doesn't plug in. Host is unreachable Q: When I ping the server using one of the clients it says the host is unreachable. Why? A: 1) Make sure all machines are on the same local subnet and no routers in between. 2) Check the lmhosts file to make sure that you do not have an outdated file. Ping lists a public IP instead of private IP Symptom: when you ping a LAN computer like ping chicagotechpc1, you may receive a public ip 64.176.153.103 instead of the computer private IP 192.168.1.100. Cause: Incorrect DNS settings. For consultants, refer to case 060104RL But I don't know WHAT is wrong with the DNS setting and I couldn't fine case 060104R on this website. Do you know how to do that? Thanks, Chas "Robert L. (MS-MVP)" wrote: We have a TCP/IP settings issue here. Posting the result of ipconfig /all on Vista may help. Also you may want to check this search result. troubleshooting ping issues Ping lists a public IP instead of private IP. Symptom: when you ping a LAN computer like ping chicagotechpc1, you may receive a public ip 64.176.153.103 ... www.chicagotech.net/troubleshootingping.htm -- 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 "chasgl" wrote in message ... I have XP machines on a home network where all the networking is OK. I'm having such a variety of problems with the Vista on the network though. I have XP machines at IP addresses 192.168.1.50 (static) and 192.168.1.103 (current dynamic) they can ping back and forth and can ping my Vista at 1092.168.1.102 (current dynamic). But when I ping the XP machines from the Vista it times out. This, I think, is new behavior even though I haven't changed things recently. If I ping an XP to another XP by name it works. If I ping an XP from the Vista by name it tries to ping 207.69.131.10 this behavior has been around forever. The Vista is configured to be on a private network and to allow file sharing. Amy ideas? Thanks, Chas
|
|
November 8th 08, 01:09 AM
posted to microsoft.public.windows.vista.networking_sharing
|
|||
|
|||
|
Now pinging isn't ever right XP to Vista
You may try to enable NetBIOS over TCP/IP first.
-- 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 "chasgl" wrote in message ... Many of my problems went away when I got my NOrton Firewall configured to allow access. The pinging by IP address works now. But pinging from the VIsta by name still doesn't work. When I followed you link I found the entry Troubleshooting Ping Can't ping another computer because of the ICF Can't use ping Can't ping outside IP or name Error code 65, 10043, 10050 and 10091 transmit failed Destination not unreachable Hardware Error Host is unreachable Pinging host name display FQDN Ping lists a public IP instead of private IP Receiving a reply from a different IP TTL expired in transit Can't ping another computer because of the ICF Sometimes, XP's built-in Firewall may enable after running network setup wizard on LAN connections. You can't ping or access the XP computer. To disable the XP firewall on the connection, go to the properties of the Connections, select Advanced, and deselect the firewall. Can't ping outside IP or name If you can't ping outside IP, make sure you have correct gateway. If you can't ping outside computer name or web name, check the DNS settings. Can't use ping If you cannot use ping successfully at any point, confirm that: 1)The computer was restarted after TCP/IP was configured. 2) The IP address of the local computer is valid and appears correctly on ipconfig /all. 3) IP routing is enabled and the link between routers is operational. 4) For the security reasons, many organizations block the return of ICMP (ping) packets so that ping or tracert may not be possible to obtain a response. Error code 65, 10043 and 10050, transmit failed Symptoms: When using ping command, you may receive either of the following: "Transmit failed, error code 65" or "Transmit failed, error code 10050" Resolutions: make sure your firewall, NAT or router doesn't disable ping and to allow ICMP Echo and Echo Reply packets. Hardware Error Symptom: when you try to ping an IP, you may receive "hardware error" reply. Causes: 1. Bad NIC. 2. The cable doesn't plug in. Host is unreachable Q: When I ping the server using one of the clients it says the host is unreachable. Why? A: 1) Make sure all machines are on the same local subnet and no routers in between. 2) Check the lmhosts file to make sure that you do not have an outdated file. Ping lists a public IP instead of private IP Symptom: when you ping a LAN computer like ping chicagotechpc1, you may receive a public ip 64.176.153.103 instead of the computer private IP 192.168.1.100. Cause: Incorrect DNS settings. For consultants, refer to case 060104RL But I don't know WHAT is wrong with the DNS setting and I couldn't fine case 060104R on this website. Do you know how to do that? Thanks, Chas "Robert L. (MS-MVP)" wrote: We have a TCP/IP settings issue here. Posting the result of ipconfig /all on Vista may help. Also you may want to check this search result. troubleshooting ping issues Ping lists a public IP instead of private IP. Symptom: when you ping a LAN computer like ping chicagotechpc1, you may receive a public ip 64.176.153.103 ... www.chicagotech.net/troubleshootingping.htm -- 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 "chasgl" wrote in message ... I have XP machines on a home network where all the networking is OK. I'm having such a variety of problems with the Vista on the network though. I have XP machines at IP addresses 192.168.1.50 (static) and 192.168.1.103 (current dynamic) they can ping back and forth and can ping my Vista at 1092.168.1.102 (current dynamic). But when I ping the XP machines from the Vista it times out. This, I think, is new behavior even though I haven't changed things recently. If I ping an XP to another XP by name it works. If I ping an XP from the Vista by name it tries to ping 207.69.131.10 this behavior has been around forever. The Vista is configured to be on a private network and to allow file sharing. Amy ideas? Thanks, Chas
|
|
November 8th 08, 04:47 AM
posted to microsoft.public.windows.vista.networking_sharing
|
|||
|
|||
|
Now pinging isn't ever right XP to Vista
Thanks, I gave that a try. But it didn't help. Chas "Robert L. (MS-MVP)" wrote: You may try to enable NetBIOS over TCP/IP first. -- 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 "chasgl" wrote in message ... Many of my problems went away when I got my NOrton Firewall configured to allow access. The pinging by IP address works now. But pinging from the VIsta by name still doesn't work. When I followed you link I found the entry Troubleshooting Ping Can't ping another computer because of the ICF Can't use ping Can't ping outside IP or name Error code 65, 10043, 10050 and 10091 transmit failed Destination not unreachable Hardware Error Host is unreachable Pinging host name display FQDN Ping lists a public IP instead of private IP Receiving a reply from a different IP TTL expired in transit Can't ping another computer because of the ICF Sometimes, XP's built-in Firewall may enable after running network setup wizard on LAN connections. You can't ping or access the XP computer. To disable the XP firewall on the connection, go to the properties of the Connections, select Advanced, and deselect the firewall. Can't ping outside IP or name If you can't ping outside IP, make sure you have correct gateway. If you can't ping outside computer name or web name, check the DNS settings. Can't use ping If you cannot use ping successfully at any point, confirm that: 1)The computer was restarted after TCP/IP was configured. 2) The IP address of the local computer is valid and appears correctly on ipconfig /all. 3) IP routing is enabled and the link between routers is operational. 4) For the security reasons, many organizations block the return of ICMP (ping) packets so that ping or tracert may not be possible to obtain a response. Error code 65, 10043 and 10050, transmit failed Symptoms: When using ping command, you may receive either of the following: "Transmit failed, error code 65" or "Transmit failed, error code 10050" Resolutions: make sure your firewall, NAT or router doesn't disable ping and to allow ICMP Echo and Echo Reply packets. Hardware Error Symptom: when you try to ping an IP, you may receive "hardware error" reply. Causes: 1. Bad NIC. 2. The cable doesn't plug in. Host is unreachable Q: When I ping the server using one of the clients it says the host is unreachable. Why? A: 1) Make sure all machines are on the same local subnet and no routers in between. 2) Check the lmhosts file to make sure that you do not have an outdated file. Ping lists a public IP instead of private IP Symptom: when you ping a LAN computer like ping chicagotechpc1, you may receive a public ip 64.176.153.103 instead of the computer private IP 192.168.1.100. Cause: Incorrect DNS settings. For consultants, refer to case 060104RL But I don't know WHAT is wrong with the DNS setting and I couldn't fine case 060104R on this website. Do you know how to do that? Thanks, Chas "Robert L. (MS-MVP)" wrote: We have a TCP/IP settings issue here. Posting the result of ipconfig /all on Vista may help. Also you may want to check this search result. troubleshooting ping issues Ping lists a public IP instead of private IP. Symptom: when you ping a LAN computer like ping chicagotechpc1, you may receive a public ip 64.176.153.103 ... www.chicagotech.net/troubleshootingping.htm -- 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 "chasgl" wrote in message ... I have XP machines on a home network where all the networking is OK. I'm having such a variety of problems with the Vista on the network though. I have XP machines at IP addresses 192.168.1.50 (static) and 192.168.1.103 (current dynamic) they can ping back and forth and can ping my Vista at 1092.168.1.102 (current dynamic). But when I ping the XP machines from the Vista it times out. This, I think, is new behavior even though I haven't changed things recently. If I ping an XP to another XP by name it works. If I ping an XP from the Vista by name it tries to ping 207.69.131.10 this behavior has been around forever. The Vista is configured to be on a private network and to allow file sharing. Amy ideas? Thanks, Chas
|
Linear Mode
