Help with Local Access only

[Jace0207]

all those problems were on several machines ... 2 and 3 were on a machine that i ordered a new mobo for and the mobo I ordered was bad, the replacement came and it was fine. 5 and 6 were another machine that had a virus, that also got resolved. 4 was a friends laptop, mouse was bad. 1 is my son's computer ... not resolved. I will try to get the pictures later today when I get back from work.

 

[DelJo63]

Microsoft diagnostic sequence

To use the ping command, follow these steps:

1. Ping the loopback address to verify that TCP/IP is installed and correctly configured on the local computer. To do this, type the following command:
   ping 127.0.0.1
   If the loopback test fails, the IP stack is not responding. This problem may occur if any one or more of the following conditions is true:
   * The TCP drivers are corrupted.
   * The network adapter is not working.
   * Another service is interfering with IP.
2. Ping the IP address of the local computer to verify that the computer was correctly added to the network. If the routing table is correct, this procedure just forwards the packet to the loopback address of 127.0.0.1. To do this, type the following command:
   ping IP address of local host
   If the loopback test succeeds but you cannot ping the local IP address,
   there may be an issue with the routing table or with the network adapter driver.
3. Ping the IP address of the default gateway to verify that the default gateway is working and that you can communicate with a local host on the local network. To do this, type the following command:
   ping IP address of default gateway
   If the ping fails, you may have an issue with the network adapter, the router or gateway device, the cabling, or other connectivity hardware.
4. Ping the IP address of a remote host to verify that you can communicate through a router. To do this, type the following command:
   ping IP address of remote host
   If the ping fails, the remote host may not be responding, or there may be a problem with the network hardware between computers.
   To rule out an unresponsive remote host, use Ping again to a different remote host.
5. Ping the host name of a remote host to verify that you can resolve a remote host name. To do this, type the following command:
   ping Host name of remote host
   Ping uses name resolution to resolve a computer name into an IP address. Therefore, if you successfully ping an IP address but you cannot ping a computer name, there is a problem with host name resolution, not with network connectivity. Verify that DNS server addresses are configured for the computer, either manually in the properties of TCP/IP, or by automatic assignment. If DNS server addresses are listed when you type the ipconfig /all command, try to ping the server addresses to make sure that they are accessible.

excerpt from MS KB314067

 

[DelJo63]

let's clear the ARP cache

using Admin Login and run->cmd, enter

netsh interface ip delete arpcache

netsh int ip reset c:\resetlog.txt​

and follow-up with the c:\resetlog.txt file please

 

[Jace0207]

Ok here is the jpg and the txt logs. couldn't clear the arp cache though

 

[Jace0207]

Well even though I was logged in as ADMIN it wouldn't let me delete the cache. So I turned off UAC and then deleted the cache but for some reason I couldn't find the txt file ... Anyway clearing the cache seemed to do the trick. I have full connectivity and ability to browse. Thanks for all the effort Joe ... I really appreciate the help. I am sure my brother would want to say thanks too he REALLY, REALLY appreciates it

 

[DelJo63]

wow! clearing the arp cache solved the issue? amazing :wave:

those routing tables are a nighmare (both of them) but if you're sorted out
and your browser fetches pages - - you're done.

suggest you

1. use ADMIN to take a backup of System State
2. also get a System Restore point
3. and then ONLY use a UAC account to access the Internet, Never the Admin account

 

[Jace0207]

No idea how the routing tables could have become so screwed up. Well it worked for a few days and now it is down again. Quite frustrated, thinking about just doing a re-install of Vista

 

[DelJo63]

suggest you see the Virus & Malware Removal 8 Step process