Hello, Ok...I have a win2k server, and a win2k client(someday, hopefully). What does it mean when I can't ping the server from the client. I have DHCP, DNS, Active directory all set up. I added the user to active directory. The client can't connect or ping the server. It gets an IP address that's not even in my scope. I've installed server 3 times and cannot get it to work?! They're connected through a small 5 port hub. No internet...I just want the client to be able to log on to the server. I even set up routing and ras on a recomendation from a friend of mine and still nothing? I was having problems with a win98 client, so I thought win2k would be easier, but it doesn't work?!?! Thanks for any help. I did ipconfig /all and here is what I got: Client ------- Windows 2000 IP Configuration Host Name . . . . . . . . . . . . : thisone Primary DNS Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Broadcast IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : D-Link DFE-530TX+ PCI Adapter Physical Address. . . . . . . . . : 00-50-BA-B8-8B-55 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Autoconfiguration IP Address. . . : 169.254.45.17 Subnet Mask . . . . . . . . . . . : 255.255.0.0 Default Gateway . . . . . . . . . : DNS Servers . . . . . . . . . . . : ----------------------- Server ------ Windows 2000 IP Configuration Host Name . . . . . . . . . . . . : server1 Primary DNS Suffix . . . . . . . : server.com Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : Yes WINS Proxy Enabled. . . . . . . . : NO DNS Suffix Search List. . . . . . : Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Network Everywhere Fast Ethernet Adapter Physical Address. . . . . . . . . : 00-03-6d-1f-c2-68 DHCP Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 10.10.1.1 Subnet Mask. . . . . . . . .. . . : 255.0.0.0 Default Gateway . . . . . . . . . : DNS Servers . . . . . . . . . . . : 10.10.1.1 someone has indicated that The 169.254.xxx.xxx address the client machine is getting indicates that your DHCP server is not working. so how do i proceed from here to get connected to the web???

Ok...the 169 address is an APIPA address and it does mean you're not receiving your IP info from DHCP. Here's what I would do. Reinstall your server and don't upgrade it to a DC until you have your network working properly. With only one client you don't need DHCP so I would statically assign IP's...but that's me, maybe you feel you have to use DHCP just because it's there...I don't know. If you wish to use RRAS/NAT to share your internet then you really don't need DHCP as RRAS/NAT has a built in DHCP setup which you can (and likely will want to) enable to assign IP's to your clients. The most important thing is to get your network and internet sharing working before you integrate AD and create a domain.

Also, you will want the NIC on your server that is connected to the internet to be getting it's IP automatically from your ISP. If you don't get an IP assigned from your ISP, you'll never connect to the internet.