Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Server can not get on the internet. Please help!

Status
Not open for further replies.

Angee

MIS
Joined
Jun 24, 2002
Messages
1
Location
US
I am an entry level technician. I tried to get online from my server (advanced server 2000)and cannot. My settings are correct, (IP, Subnet, Gateway, Preferred and Alternate DNS). I have 7 local machines that I assigned static IPS and now they are obtaining IPS and DNS automatically. I have a cisco router that connects to a 10/100 hub. The lights on the hub show that they are recieving. (light blinks once in a while) The LAN on my server shows that it is recieving but not sending. The NIC shows a link light on the server. Can someone help me please.
 
I think the first thing I would do is try the trace route command to see where the hang-up is.
go to the dos prompt and type the command:
tracert microsoft.com

Does it get to your router?, past your router? where does it hang up?

Can your router pass information back to you? Are you on a different subnet? Does the router know about your subnet?

Try these and see what happens.
 
Also, I would make sure that you were able to ping the LAN and WAN interfaces on the router.... assuming that you didn't block icmp packets on the router. Let us know what happens.....


from DOS:
ping <LAN ip>
ping <internet side IP>

Post the results...


burke
 
I can ping an external IP address from the server that the router is attached to but not from a client PC. When I issue a tracert command from server or clients e.g. tracert microsoft.com I get "Unable to resolve target system name microsoft.com".

Any clues?

Thanks

Dan
 
check the duplex settings on your server. make sure they are set to auto. if they are set to full and you are plugging into a hub (half duplex) you could experiencing problems like this.

also issue a ping from your server and watch the packet counters in the network connecitons sections for the sending. they should increment even if you are not getting an echo reply. the interface itself should still attempt to send it and thus increment the counters unless it is bad. also check your cable. you can get a link light and still not be able to pass traffic with a bad cable. rare but i have seen it.

Lui3
CCNP,CCDA,A+/Net+
Cisco Wireless Specialization
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top