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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

pinging problem!

Status
Not open for further replies.

port27374

Technical User
Feb 14, 2004
41
hi folks,

after recently designing and building a small network i installed win XP Pro on all 16 client machines and windows 2003 server standard on the server ( at the moment there is nothing else in the network). i wanted to set the server up as a DHCP server and a DNS server - so i accordingly added some roles to the server through "manage your server wizard" this included making it a domain controller... for some reason the clients were not able to obtain IP addresses from this server. at first i thought it was a configuration problem, but then i started investigating the issue further as basic troubleshooting didnt work... eventually i ended up removing all the roles of the server and made it a simple server with no added roles, i also made sure i rebooted client and server machines. to see if i could get connectivity through the network by pinging the clients from the server, no luck....

i then tried to ping the clients from each other, this worked fine, eliminating the posibility of a faulty switch. all link connections on my 24 port allied telysyn switch show up fine.

i tried a completely different switch and connection just the server machine and another PC to see if they will ping each other, but no joy. i can basically ping everything else on the network when i assign it a static ip address and its in the same "workgroup"... but the server doesnt respond.. i just always get a "Request time out" response when pinging to the server and from the server.

all the drivers on the server seem fine, i installed the network adapter driver fro the CD i had with the A-bit IS7 MOBO... the device manager show no problems or conflcts. ive eliminated the posibility of bad cables through swapping the orignal server patch cable with one i tested previously but no luck...

non of the windows installation have been "activated" yet, and they all have 26 days left. i have 20 CALS and am using then in Per Server mode. i dont know if this makes any difference to network connectivity, but i thought i would mention it anyway.
ive also tried pinging the loopback ip 127.0.0.1 on the server and this was successful.

other info you may need to know is i have assigned the server a static ip address of 192.168.0.2 and each client has an ip address increment of xxxx.xxxx.xxxx.xxxx+1.... i.e. the first client has a static ip address of 192.168.0.3 and so forth...

any ideas? could this be a faulty network card? anyone have any ideas where i need to configure something differently?

regards
J
 
Sounds like you have the built in firewall turned on and it is blocking ICMP traffic.

I hope you find this post helpful.

Regards,

Mark
 
hi folks - just wanted to update you on this situation - the firewall was taken care of before the post so that wasnt the problem - good guess though :)

it was actually the NLB (Network Load Balancing) component of the Network components was for some reason stopping me from pinging anything else on the network.
After i uninstalled the NLB component i could successfully ping all the other machines! i have onle one NIC in the server so i dont know why NLB was installed. oh well - problem solved

thanks
bye
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top