Internet problems and DNS configuration

  • Thread starter Thread starter Joeb
  • Start date Start date
J

Joeb

I have recently had to rebuild a windows 2000 Server after a hard drive crash.

Since i have done this I have been having trouble with clients not getting
internet access and clients not logging on correctly.

The server address is 192.168.0.1.
The subnet is 255.255.255.0
The gateway address is 192.168.0.254 (this is the address of a small ADSL
modem on the network.
The DNS addresses are 192.168.0.254 and 192.168.0.1 on the server.

The server itself connects to the internet fine. Other clients seem to work
for a little while and then stop for no apparent reason. If the computer is
restarted the internet works again for about 10 mins and then stops.
When I check the event viewer for most clients they don't seem to be logging
on correctly. ie autoernrollment error messages and userenv both saying that
the domain controller could not be found.

I believe the issue may be with the DNS and gateway settings but if i change
everyhting back to point to the server at 192.168.0.1 the internet does not
work.

I also added a reverse lookup zone on the server but not sure if that would
be the cause of the internet working on some clients for a short period of
time and then stopping.

Does anyone have some ideas on what i could do to fiz the problems.
 
Hello Joeb,

Is it a domain controller? If yes, have you readded the clients to the domain?
Please post an unedited ipconfig /all from the server and one client. Have
you configured a forwarder in the DNS server properties under the forwarders
tab?

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
 
Hello Meinolf,

Yes it is a domain controller. I have not configured a forwarder. What do i
have to configure in this area. When you say forwarder , do you mean forward
to a router or modem address.

The server is also a DHCP server. I have configured the router/modem address
in the scope options. Is this correct.
regards
 
Hello Joeb,

I would set it up like this:

Server IP 192.168.0.1
Server SM 255.255.255.0
Server DG 192.168.0.254
Server DNS 192.168.0.1


DHCP scope options:

Default gateway 192.168.0.254
DNS server 192.168.0.1
DNS Domain name yourdomain.com


Open the DNS management console, rightclick the servername, open the properties,
go to the forwarders tab and fill in your ISP's DNS server ip. The clients
will query your internal DNS server, if this can't resolve the address it
will forward to the DNS server from your ISP.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
 
Hi Meinolf,

Thanks for the info. When I go to the forwarders tab of DNS properties, it
is all greyed out. There is a message there which says forwarders are not
available because this is a root server.

As far as I know I set it up as a domain controller. There is another
windows 2000 server on the network which acts a sa print server but this is
not a PDC.

When i was configuring this current server i made sure that I disconnected
the other print server from the network so that it would not be detected.

Can I change the server to not be a root server. what difference does this
make.

regards
 
Hello Joeb,

To get it free, just delete the .zone in the DNS management console, close
the DNS console open it again and you can configure the forwarder. The root
servers in this case are the internet root server, so you can delete the
..zone it without any problem. Did it myself more often.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
 
In
Meinolf Weber said:
Hello Joeb,

To get it free, just delete the .zone in the DNS management console,
close the DNS console open it again and you can configure the
forwarder. The root servers in this case are the internet root
server, so you can delete the .zone it without any problem. Did it
myself more often.
Best regards

Meinolf Weber
Click to expand...


Here's a reference for Joeb in case he has questions concerning this or not
sure how to, as well as some additional info:

323380 - HOW TO Configure DNS for Internet Access in Windows Server 2003
(forwarding) :
http://support.microsoft.com/?id=323380


--
Regards,
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT,
MVP Microsoft MVP - Directory Services
Microsoft Certified Trainer

Infinite Diversities in Infinite Combinations
 
Hi thanks for your help in this matter. I setup the server IP details as per
instructed and then deleted the .zone , setup a forwarder to the ISP DNS
server and all is working fine now.

Is this a standard procedure to setup a server whether it be 2000/2003
server.

I have done other installations where I did not do this but it still seems
to be working good.
 
In
Joeb said:
Hi thanks for your help in this matter. I setup the server IP details
as per instructed and then deleted the .zone , setup a forwarder to
the ISP DNS server and all is working fine now.

Is this a standard procedure to setup a server whether it be 2000/2003
server.

I have done other installations where I did not do this but it still
seems to be working good.
Click to expand...

Yes it is standard, more of a best practice, pretty much.

Now you said with the DOT zone that you still had internet resolution? Were
you using an ISP's DNS in IP properties? If a DOT zone existed, the only way
to get internet resolution to work is if you were using an additonal ISP DNS
in IP properties. No need to say what that can do to AD.

Cheers!

Ace
 
Back
Top