We have set up a windows 2003 server network with one server, 3 workstations and 3 laptops. The problem is that the workstations cannot connect. If you disconnect the ethernet cable the machine logs in normally then you plug the ethernet cable back in and you are on the network. We have active dir, dhcp, dns, and terminal server running on this box. When a computer tries to log onto the network it takes about 4 minutes to get to the applying computer settings screen and then take 30-40 minutes to finish connecting. We are running all computers through a D-Link DI-707P router and have a dsl modem to provide internet. As soon as the workstation gets to the applying computer settings screen you can see it in network neighborhood. You can ping it but you get a wierd IP if you ping it by name. Example workstation named workshop. Ping workshop from the server and you get a 64.15.0.whatever and we should be getting a 192.168.0.whatever. Does anyone have any idea what I have done wrong? Please email me.

My guess is Group Policy/Active Directory. Start with one server and one computer and go from there. Post more on setup on the server. I prefer static IP's.

If you get a weird ip address on a ping command then proberly your DNS server is not configured correctly. Ping is based on winsock and winsock relies on DNS. Check the DNS server and see if there is an A record for the specific host. You can also check if WINS is working correct by typing NBTSTAT -A 192.168.*.* (this is the ip adres of the specific client) If the respons shows the right computername that belongs to the specified IP adres WINS is working correctly.

Check to make sure that your router is not configured to be handing out IP addresses as well. That could be part of the problem. Let the server handle dhcp, set the router with a reserved, static ip address and use it as a gateway. You may have checked this, but I didn't catch it in your description if you did.