Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
I have a windows 2003 server running dhcp for sharing internet among client computers. Occassionally the clients will be limited to only some websites (domains) while the server can still access them. It seems to happen at random and requires a reboot of the server so that clients can continue browsing again. Also I noticed that if a server accesses a website (domain) then the client will be allowed to!
Thanks in advance!
Andrew
I have seen this issue on internal DNS servers before. It seems that your DNS on the server decides to crap out at times.
This seems to be a frequent issue on 2003 and 2008 servers any more.
I would commend restarting the DNS Server service at least once a week on 2003 and 2008 servers.
Your better off creating a batch file to do it for you.
Create a batch file:net stop "DNS Server"
net start "DNS Server"Scedule a task to run the batch file weekly.
0 
thanks warneir I will try that.
Also I noticed I can restart the modem sometimes and this fixes the problem again, not always have to restart 2003.
0
to ad to this, Windows is not setup as my DNS server, I believe the DNS server is the one inbuit in the Router?
0
"This seems to be a frequent issue on 2003 and 2008 servers any more."
Interesting observation. Simply not the norm for MS dns server. I would suspect a misconfiguration instead.
hampsterman your dns configuration is incorrect. There is no dns server in the router. You are just pointing dns to the gateway hoping the isps dns server will respond to the request.
Workstations should point to the ms dns server.
MS dns server forwarders field is occupied by entries for your isp dns servers so it can forward internet requests to them for resolution.Your setup does not allow local name resolution since the isps internet servers have no knowledge of your server or workstations. Local name resolution can only occur due to broadcasts [last act of desperation to resolve a name]
Best configuration is to have ms dhcp dynamically update ms dns.
If your isps dns servers are having problems include in the forwarders tab another dns server not associated with the isp.
0
"MS dns server forwarders field is occupied by entries for your isp dns servers so it can forward internet requests to them for resolution."
Perhaps thats the issue, ideally I thought everything should work fine without setting this up? How can I set this up, I'm basically a server noob.
0
Microsoft designed their server system [AD] to use DNS for name resolution. Workstations make a request for a local name the dns server resolves it. If the workstation makes a internet name request the ms dns server forwards it to the dns server listed in the forwarders tab. The internet dns server returns the answer to the ms dns server which then responds to the workstation.
this should help
http://support.microsoft.com/kb/323380
0
If the server is runnig AD then DNS is already installed.
"This seems to be a frequent issue on 2003 and 2008 servers any more."
Yes this is a interesting observation.
But here are the facts.
I work with over 300 clients. (it does not happen to all clients. Its random.)
The symtom is more frequent in 2008 server then 2003.
DNS was set up on the servers during the install of AD. (yes the wizards were used in 2008. since every time you run a command it doesnt set permissions properly.) So a misconfiguration would be a little rough to do.The symtoms started after 2008 was released and updates were installed. I have been attemping to track what update maybe causing the issue, but its a little rough to do when it is random times that the DNS starts acting up.
I have just gotten into the habit of scripting the restart of DNS at night.
0
"I have just gotten into the habit of scripting the restart of DNS at night"
How can I do that?
You said that I have it setup incorrectly however I don't need local name resolution, so why do I need to setup a DNS on the Server?
0
why do you think you don't need local name resolution?
you have a server right? Running Active Directory?
0  |
 |
 |
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
