Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

New WIN2K setup and issues login and DNS

Status
Not open for further replies.

Corneliu

Technical User
Sep 16, 2002
141
US
We had a Wint NT 4.0 server that died a few days ago. We purchased a new server with WIN2K.
The prior setup was a follows:
WIN NT 4.0-WINS-PDC-DNS IPs from ISP
CLIENTS Static IPs-DNS from ISP- Gateway same as PDC

The current server is WIN2K, and we have problems adding the clients on the PDC. This is the setup:

WIN2K Server
DHCP 192.168.1.10-60
DNS IPs from ISP
WINS 192.168.1.2
Gateway 192.168.1.1
IP 192.168.1.2

Clients:
Static IPs- Some DHCP (for some reason some users DID NOT want to get the IPs from the PDC, this is a mixed enviroment, ME, XP, NT 40 Workstation, etc)
DNS IPs from ISP
Gateway 192.168.1.1

Now this is the problem:
When I try to add the clients to the PDC, it will not find it and I cannot add the workstations.
If I add the PDC's DNS IP to the client PCs, than the PCs cannot access the internet. (each PC before had the ISP's DNS info in TCP/IP settings and can access the internet at any time).
I cannot ping the PDC by name either.
I know maybe I do something wrong, but I just cant seem to find the problem. The NetBIOS is disabled on server and clients. I tried (on the client side) to have the Primary DNS as PDC IP and the Secondary from ISP, but that did not work either. Than I tried Primary DNS as the PDC IP and secondary nothing, and that did not work either.
Now, I was able to add one PC to the domain for some odd reason yet the same settings as the other clients, BUT it took approx 5 minutes to login.

I set networks up before but never seen nor had this type of problem before. Anyone can help me with this PLEASE?????

We took over the IT part of the company a few days ago and only had 2 days to gather information from the previous guys, than the server just crashed.

Please please any help I would appreciate it very much.
 
Hi,

You can try to search in this forum with keyword DNS

thread96-703112
 
Can you verify something here?

What role is the Windows2000 Domain Controller playing? Is this an NT4 domain or a mixed Windows2000 domain? Did you introduce the Windows2000 Server into the NT4 environment as a Member Server? All this plays into how DNS and DHCP and the clients connect. Is this the only Domain Controller in your environment? Need more info on how your domain is setup before commenting further. Seems like your DNS Server is not working properly and/or your DHCP server is not configured properly. When you install Windows2000 Server as a Domain Controller (I.E - promoting this via DCPROMO) you have to setup a DNS Server. Did you set this up? Assuming that you do have a DNS Server make sure you have your servers DNS IP Settings (Via TCP/IP Settings)pointing to itself (again, only if this is the first Windows2000 Domain Controller you have installed in your environment). Do an NSLOOKUP at the command prompt on the server. What response do you get? If you get a good reply from the NSLOOKUP note what this is. If you are using Static IP on the clients make sure you have the DNS IP Address and DNS Suffix pointing to the DNS Server. If your clients are configured to use DHCP make sure the DHCP Server options 006 + 015 (DNS Entries) and 044 + 046 (WINS Entries) are configured correctly. Also if you have a router (I believe the entrie is 001) make sure this is setup correctly. Also, on the DNS server for your clients Internet Access you need to check the following. Check to make sure you do not have a "." zone. If you do you need to delete this zone. You need to do this so you can configure the "Forwarders" tab (which is greyed out if you have a "." zone setup). On the Forwarders tab you need to enter the IP Address of your ISP (This helps resolve the clients internet).

Sorry for the long winded notes here. Hope I helped. My recommendation would be to use DHCP (not static). Increase the IP Scope and use DHCP if you can. Again, verify your DNS and DHCP (if your environment is Windows2000).
 
try adding the internal dns and the default gateway as dns entries on the workstation.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top