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
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