VPC 7.0.2 no internet

First thing to try when you cannot ping by url (www.yahoo.com) would be
to add a DNS server in Local Area Connection > Properties > TCP/IP
Properties. Since you CAN ping 4.2.2.2, then add that ip address as the
primary DNS server address (it's Yahoo's public DNS server).

The MTU fix is used when you can ping BOTH the ip address and the url
but cannot access some websites (like any Microsoft site).
 >> Stay informed about: VPC 7.0.2 no internet 

Thanks for the suggestions. Here's where I'm at:

1. ping 4.2.2.2 Works.
2. ping my ISP's DNS 211.29.132.12 Works.
3. In XP, manually set the DNS to the above (and restarted XP). IE DNS
error.
4. ping yahoo.com Fails
5. ping -f -l 1500 4.2.2.2 "packet needs to be fragmented" error.
6. ping -f -l 1492 4.2.2.2 "packet needs to be fragmented" error.
7. ping -f -l 1454 4.2.2.2 Works.
8. Set the MTU in regedit to 1454.
9. Restart XP.
10. ping -f -l 1454 4.2.2.2 "packet needs to be fragmented" error.
11. Set MTU of 1400 in regedit.
12. Restart XP.
13. ping -f -l 1400 "packet needs to be fragmented" error. Ugg!
14. Set MTU of 1000 in regedit.
15. Restart XP...

Whatever I set the MTU to, after restart, that same amount pinged gets the
"packet needs to be fragmented" error.

Any suggestions at all most humbly appreciated!

Anthony
--
Please reply to this message within the thread instead of emailing them to
me. Thanks!
 >> Stay informed about: VPC 7.0.2 no internet 

Leave the MTU value set at 1454 in the Registry.

Add 4.2.2.2 as the DNS server in Windows (it's the public DNS server
for Yahoo)

Restart Windows.

Open IE. try going to www.red.com or www.purple.com
 >> Stay informed about: VPC 7.0.2 no internet 

Thanks for the suggestion, but still no internet access...

To make sure that any of my previous tinkering with XP connection settings
were wiped, I uninstalled the virtual NIC in Device Manager, restarted and
let XP find the hardware and automatically create the Local Network
Connection. I changed the MTU, and the DNS settings and restarted, but no
joy...

Anthony

PS I did notice in Regedit when adjusting the MTU to 1454 that all three of
the Interfaces have the IPAddress of 0.0.0.0, although the one for the
virtual NIC (I'm assuming) is the one with DhcpServer, DhcpSubnetMask etc
values... I thought it should have an Ipaddress...



in article 1129308245.575366.27300.RemoveThis@g49g2000cwa.googlegroups.com, Paul Power
at paulkpower.RemoveThis@gmail.com wrote on 15/10/05 2:44 AM:

> Leave the MTU value set at 1454 in the Registry.
>
> Add 4.2.2.2 as the DNS server in Windows (it's the public DNS server
> for Yahoo)
>
> Restart Windows.
>
> Open IE. try going to www.red.com or www.purple.com
>

--
Please reply to this message within the thread instead of emailing them to
me. Thanks!
 >> Stay informed about: VPC 7.0.2 no internet 

Well, now that you've disclosed that you removed the NIC from Device
Manager, you're obviously on the wrong track as far as MTU settings are
concerned. You do not have an IP address on the Windows side!! So,
you're never going to get any kind of connection until an IP address is
obtained.

Go to Network Connections and look at the Local Area Connection.
Directly under it, does it say 'disabled', 'enabled', 'connected', or
'disconnected'? What does it show for a NIC?

If it shows connected, you do have an IP address. Go to a command
prompt and type ipconfig /all. Make note of the ip address and default
gateway as well as the dns server address. If you're using Shared
Networking and have not messed around with adding any kind of IP
address in the TCP/IP properties, it should read:
IP Address: 192.168.131.65 (the last octet may be different)
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.131.254
DHCP server: 192.168.131.254
DNS server: 192.168.131.252

If these values are different, let us know. Do NOT manually assign any
of the above values.

By the way, you would not be able to ping anything without an IP
Address.
 >> Stay informed about: VPC 7.0.2 no internet