NIC problem..

I do google alot.. I looked up, "bad NIC card symptons".. "NIC gets IP but no internet access".. etc.. Still stuck, i tried all the suggestions.. unistalling card in device manager, resetting modem, a different patch cable, disable/enable card, ping google.com (didnt ping IP yet,) reseated card.. =/ sorry for attitude earlier.. but yes netowrking is my weak point.. Still learning those and servers.
 
I have had a similar issue come up before with a system that was running Symantec Endpoint Protection that was allowing allowing internal access, but blocking access to wan. Sometimes these can be really frustrating to troubleshoot, take a deep breath, and begin a systematic approach to possible causes and begin checking them off. Once you have eliminated hardware as an issue, begin looking at the software side.

Learning is a great experience, good luck.

Brian
 
When it comes to business computers.. Do you stay onsite for all the work? This is his only PC, should i offer to take it to office so I can work on it or stay there?

When I go back at 530 today I'm going rebuild IP stack and see if it helps..
 
Last edited:
This is his only PC, should i offer to take it to office so I can work on it or stay there?
Click to expand...

Depends on the situation. If you're having trouble getting it back online and you know it's the machine and not anything else in the network, you might suggest that you take it so you can pinpoint the problem. The real key is making sure it is the PC and not something like the modem/router. The worst thing to happen is that you get it to your shop and it connects to the internet as soon as you plug it in.


If you can ping 209.85.225.99 (Google), it's probably something on the system. Messed up DNS settings. From there you can try setting OpenDNS manually to see if it works or rebuilding the tcp/ip stack. You might find it's a quick fix. Beyond that, it might be worth taking it with you so that you can have time to figure it out without as much pressure.
 
14049752 said:
If you can ping 209.85.225.99 (Google), it's probably something on the system. Messed up DNS settings. From there you can try setting OpenDNS manually to see if it works or rebuilding the tcp/ip stack. You might find it's a quick fix. Beyond that, it might be worth taking it with you so that you can have time to figure it out without as much pressure.
Click to expand...

Will try pinging Google by IP too. Thank you
 
I would do this one onsite because i don't think it is a big enough problem to take away but if you are struggling for ideas then maybe it will be best. Personally I would try and stay on after work hours or look at it through his lunch break so you haven't got him watching you.

Basically you need to see if it is a dns problem by pinging by name and look to make sure it resolves the name to ip(will be in brackets). If it does then do a tracert to an ip address(tracert 1.1.1.1)in a cmd window and see how far it goes, certainly beyond the default gateway. It should go off looking on the net. Once that is done and ok you're back to your computer really.
 
Last edited:
Well are you sure you haven't got a problem with the switch port/cable/card? Try pinging the default gateway with large ethernet packets.

go to cmd

ping <default gateway IP> -l 1500 -t and let that run and see if you get packet loss.
 
Computer Brainiacs said:
take a Cymbalta... ive never had a issue ith NIC card from software.. So idk why your so confident.. I checked properties for card for stupid errors and everything.
Click to expand...

You're missing some key details here. In order to figure out where the problem is, you'll need a broader range of diagnostics/symptoms than just it's got an ip address and can't ping google.

Can you ping the default gateway? What are the dns servers? Can you ping them? Can you ping the ip address for google.com rather than just the domain name?

These are all important questions when you're dealing with a networking issue. If you can't ping the default gateway, that immediately points to either a bad cat5 cable, a bad NIC, or a bad router/modem. If the DNS servers are being obtained through dhcp, they might not be getting the correct info from the router/modem. If they're not set, that's an obvious problem. If you can ping the dns servers, you definitely have internet connection, and points to a DNS problem. Same goes for if you can ping google.com's ip address, but not google.com. DNS servers translate a domain name into an ip address, and if you can ping the ip address, the breakdown is in translating the name to an ip.

I probably forgot something, as it took me about 1.5 hours to type this up being interrupted by an irate customer(at my 9-5). But those are some pretty basic questions to ask when troubleshooting networking stuff, and a good starting point to be able to come here with enough info for someone to be able to answer questions rather than just having to ask more questions.
 
14049752 I missed you buddy !

To Brainiac you missed the first step.. (at least initially)

You have to approach in a logical fashion. Not doing that is hell when it comes to networking

The most important question is..

Is it Hardware or Software ?

This is what you need to figure out.

Here are some of the questions you need to ask yourself to figure out this problem.

Does the internet connection work with a known working computer?

Does the internet work within a boot cd/Safe mode?

Does a usb internet device fix the issue?

After this you know what direction to take.

I have had customers who called another tech.. and he spent hours on their networks and computers and their cable modem wasn't working properly.
 
He said cablevision was there testing the modem and line and it was fine... it also works on other computers.. the computer worked in my office right away.. not in his... its weird.. cant reach dhcp server at his office

his windows 7 was a pirated copy and it wasnt activated.
 
Last edited:
If it can't get an ip address from dhcp manually put in the details including dns. If that all it was it should have been a 2 minute job. Virtually the first thing you should try is an ipconfig /all. You can go from there then.

Post 6 highlighted where you should have spotted that. If a Windows computer cannot get an ip address from the router then it will assign an ip as noted. So when you said it had an ip address we all assumed(except poster of 6) it was one within the scope from the router. Of course the privately assigned one 169.x.x.x won't be able to communicate with the router as they would be on different subnets.
 
Last edited:
Computer Brainiacs said:
He gets an 69. IP which is what optimum normally gives ..
Click to expand...

Do you mean 169? If so that's the ip address that Windows gives out when a computer is set to Automatically Get Ip Address and it cannot find the dhcp server, in this case the router. Look on one of the other pcs and run ipconfig /all., Find the router ip address and log in and see what ip range has been set.

Ok what you can do is get a cmd window up on the problem pc and working pc. Run ipconfig /all > c:\1.txt and on the other one 2.txt and copy both those files onto here.
 
Last edited:
You must log in or register to reply here.

Similar threads

HCHTech
Narrowing down a internet issue
Replies
5
Views
560
YeOldeStonecat
YeOldeStonecat
HCHTech
GoDaddy again - Outlook error 7ita9
Replies
3
Views
219
callthatgirl
callthatgirl
C
VM Server reboot has a 169. address.
Replies
3
Views
1K
YeOldeStonecat
YeOldeStonecat
DanF
VLANs challenge
Replies
7
Views
1K
DanF
DanF
NETWizz
Ticket of the Week
Replies
1
Views
755
callthatgirl
callthatgirl
Back
Top