I'm running windows small business server 2003. When I attempt to log onto the domain from an XP workstation I get the following error: "The system can not log you on now because the domain (domain name) is not available" here's what I've tried already: the xp workstation is added to the domain and appears in active directory the server has a static IP address the server is pointed to itself for DNS the xp workstation's DNS server is set to the server's IP address the DNS service on the server is running I created an LMhost file on the workstation that points to the server my network is configured like this: internet--->dsl_modem--->airport_exterme_router--->Dlink_switch-- >windows_server The server is the DNS server but the router is the DHCP server. I tried to use the server as the DHCP server but I could not because my internet is PPPoE and the router must be configured to distribute IP addresses. I can not turn off DHCP in the router. My DSL modem does not have a firmware interface, so I can't put the PPPoE settings in the modem instead of the router. If I get a new modem and save the PPPoE settins in the modem, will the modem have to act as the DHCP server? Do I have to change my internet service to a cable modem in order to use my server as the DHCP server? If I use my server as the DHCP server instead of the router, what happens to my wireless clients who access the domain via my wireless router?

I might misunderstand your setup. No, you can't allow your dhcp to access the internet directly. Your isp outght to notice that or block it at least. No, you can not log on to a domain across the web without a VPN. You shouldn't need lmhosts unless you have legacy issues. I read it wrong and answer it wrong too. So get off my case you peanut.

"I could not because my internet is PPPoE and the router must be configured to distribute IP addresses. I can not turn off DHCP in the router." That is incorrect. DHCP server is on the lan interface. PPoE is on the WAN [not lan] interface. You can turn the dhcp server off on any soho router I have worked with. But this won't hang you up as long as the routers dhcp server is giving the workstation the correct gateway and dns server. "If I get a new modem and save the PPPoE settins in the modem, will the modem have to act as the DHCP server?" You are barking up the wrong tree. Your modem is not a nat device like the router. Don't pursue this or any of the other stuff since your modem and router are not the issue. Correct file to use is the Hosts file but I highly advise you nuke both [just rename both to *.tmp so they don't load] This just muddies the waters. Eliminate them as a source of issue since you don't need them. A wrong entry or syntax in either can result in your issue. You want DNS to resolve your names not either of these files. Is this for all workstations or just this one? Have you examined the event viewer logs on the server for errors that may point to this problem? For example make sure simple tcp/ip services is running. Make sure netbios helper and remote registry helper are enabled and running. See if you can ping the xp box from the server. Do the reverse. Post back the answers. Imagine the power if you knew how to internet search

Thanks for all the help. When I try to use the server as the DHCP server, it says there's a conflict because the airport router is distributing IP addresses. But when I go to the router and uncheck the option to distribute IP addresses, it gives me an error "Distribute IP addresses must be enabled for PPPoE" That's what I mean when I say that I can't turn off DHCP in the router. Maybe it's an Apple Airport thing... This is a new server and domain I'm setting up for the first time. I've never been able to log on. I took the server and the workstation and put them on their own hub (I tested the hub first, and it works) So now I just have the server and the workstation all by themselves connected to a hub with nothing else. I configured the DHCP service on the server and it's running. It is set to distribute 192.168 IP addresses. I configured the workstation to aquire IP and DNS automaticly. I deleted the workstation from active directory and rebooted the server and the workstation. When I do an ipconfig on the workstation, the ip address isn't 192.168 it's 192.(something different). It's not getting an IP from the server at all. I am, however, able to log on to the server with the username and password of one of my domain user accounts, so at least that works.