I'm running a W2K domain server with win 9X clients. The DC has DNS, RAS, and DHCP installed. The network uses...
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
TCP/IP. I have a remote office which connects via 2 routers and a dedicated 64K line. The clients at the remote office, using the IP address, are able to ping the server and other clients on both subnets (remote 255....252 local 255....0). Name resolution is not happening on the remote clients. It is, however, happening on the local client. The remote clients can map a shared drive (using the IP address) on the DC, but they are unable to log onto the DC. I need them to log on in order to get my policies implemented. You didn't mention WINS. You'll need a WINS server for the W9X clients. Your symptom indicates a WINS problem of some sort. Do you have more than one WINS server?
Make sure the clients in the remote office are configured to point at the DC for DNS and WINS. Check the WINS database to make sure the clients are registering.
If you ping the fully qualified DNS name of the DC, does that succeed? If so, you know you have a WINS issue and not a DNS issue. You can add a Domain name to the DNS Configuration of the TCP/IP stack and that might resolve your problem, as well. But you'll still need WINS for NetBIOS name resolution.
Dig Deeper on Microsoft Windows 2000 Server Administration
Related Q&A from John Robbins
What is a JAD session? This term is referred to often in job postings and seems like some kind of brainstorm you carry out with a client to define IT...continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.