Link to home
Start Free TrialLog in
Avatar of StewartTechnologies
StewartTechnologiesFlag for United States of America

asked on

Workstation Unable to connect to the internet.

Hello-

I have a workstation that stopped connecting to the internet. It sees the internal network,  accesses network files and resources and can send email via outlook exchange within the network, but cannot connect to the internet. The NIC adapter has a yellow caution sign indicator.

At some point during the troubleshooting process it dumped memory (blue screen)

I have updated the NIC driver
Checked the device settings for the NIC
Reset Tcpip
Performed system restore to a previous state
Ran hardware diagonostics it passed
Finally re-installed thhe OS, installed the network drivers and still thave the same issue.

It is a WIN 7 Professional DELL workstation.
Any suggestions?
Avatar of Dusty Thurman
Dusty Thurman
Flag of United States of America image

In checking the device settings on the nic, did you confirm if this is getting a dhcp address or a static one? Is it the same network the rest of the site is using for internet access? It's possible if you have a 192 address range for most pcs and something like a 172 address range for other types of devices it is on the wrong network.

Have you checked the installed firewalls? Especially the integrated windows firewall?
Have you confirmed the device has the correct gateway configured?
Avatar of StewartTechnologies

ASKER

It gets it's address from the DHCP server. You can ping it from any other computer on the network and get a reply. The workstation has access to internal files but not the internet.
Please check the gateway. Does it differ from any other PC? Internal traffic will work even if you have the wrong gateway.
Also, I would disable any outbound firewalls, like sifu said, as a test. If you have AV or anything you might have to temporarily disable it if it controls your firewall.
Looks like you have a DNS problem.

From a command line (Start menu, type CMD and enter) do the following tests:

1- First check your IP settings: "ipconfig /all". Your will get your own IP, the gateway, and DNS server(s). Note all of this.
2- Ping your own IP: "ping 172.16.157.30". Replace the IP with yours. Your should get replies.
3- Ping your gateway.
4- Ping your DNS server(s).
5- Ping an external resource: "ping 8.8.8.8". This is a Google DNS server.
6- Ping a local resource by name: "ping myserver1.acme.local". Use your server names here.
7- Ping an external resource by name: "ping www,google.com". This one always responds.

You should get replies from all of the pings above. If line 5 and below fail. You definitely have a DNS problem.

Please report back results for further assistance.

Cheers!

-XT
I performed the above ping processes

I can get a reply internally but when i ping Google or yahoo, no replies.

My IP gateway and DNS matches and is correct when i IPconfig.
ASKER CERTIFIED SOLUTION
Avatar of Metaltree
Metaltree
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I wouldn't rush to get a new NIC yet...

Please be more specific as to the result to the external pings. When pinging to names, your computer attempts to resolve the IP from its own chache and then it goes to your DNS server. If your server is not resolving the name, and it is not configured to query itself to other DNS server, it will simply reply that it does not know that name.

Are you getting an IP translated when you ping the name, and no replied from that IP, or you get an error saying that it could not find the host name?

-XT
The external pings= request timed out

Pinged google and 8.8.8.8 = request timed out.

Computer talks internally fine.
When you ping google.com does it return an actual IP address its trying to ping?
No it dosen't return an actual Ip.

just the request timed out packet lost=100%

@Metaltree you had suggested a New NIC, why please?
You have performed every possible step of troubleshooting and this is a basic workstation. Easy and cheap fix = new NIC
Do you have another workstation with similar settings that does work fine?

It could be your gateway at this point.

Do a trace route test: "tracert 8.8.8.8" and see if you get past your gateway's IP.
You said you could ping your gateway, right?

For local pings (same subnet) you gateway does not play a role in routing.

-XT
I don't agree with Metaltree at this point. I might later on, but we never did a tracert to confirm this is not a routing issue. Possibly external to the station.

-XT
xpert, its a single workstation, all other workstations are fine. So unless this single computer is plugged into a VLAN on a switch or something similar, then it has to be the NIC.

Time is money and right now, for a SINGLE workstation, the easiest/fastest/cheapest fix is a new NIC.
I have ordered a replacement Motherboard (on board NIC). After the install and test i will let you all know the outcome.

Thanks for all the input.
Metaltree, you're totally right, but at the same time, if we are not 100% sure the issue is local to the PC, like you said, it could be a VLAN, bad even a bad switch port; we could end at the same place with the new NIC.

If there is another NIC laying around that can be tested with, I would check that option out too. Also, if this station is connected to a managed switch, I'd compare the port settings with other working stations, or even move it to another port.

-XT
ST, I suppose your DELL station is not under warranty? Dell support (business) is most of the time very helpful. I've seen some weird issues with drivers off the Dell site. You could install a driver from the manufacturer directly too.

-XT
Thank you ALL.

 Replaced the Motherboard (on board NIC) and everything is fine.