Microsoft SBS 2003 Server having DNS issues
Posted on 2012-08-27
I have a Microsoft Windows Small Business Server 2003. It's up and running and appears to be working somewhat normal. Everyone can get into their data and Outlook. I basically just inherited the server from a previous IT company who has been failing supporting them. My future plans is to build and SBS 2008 server. For now I need to get this one running smoothly
I first started seeing problems when I attempted to do an online backup using MozyPro (an online data backup service). It failed consistently. I spent hours with tech support trying to resolve the problem to no avail. My personal laptop also has MozyPro and it fails on their network as well - where it works well at any other location. I even tried to change my laptop DNS server to point to the gateway of the router and it failed as well. So I knew it wasn't any proxy related issue.
As a test I removed the original router (Cisco Small Business RV 120W Router)
and installed a Cisco Linksys Wireless-N Home Router, Model WRT120N. I disabled the DHCP. Once I swapped out the router, the server started backing up successfully using MozyPro. In addition, my laptop being attached to the same LAN also backed up fine.
- Now the problem is, half of the users could not connect to the exchange server. So for now, I had to switch back to the original router. Users can now access Outlook but of course the backups of failing.
Here are some of my concerns
- I don't believe the original Cisco small business router is configured correctly or even the correct router to use in this environment. First of all I am not familiar with this router but I know the basic and required settings. The company the supported this network previously originally had a SonicWALL router but they removed it and replaced it with the Cisco small business router.
- When I look at the settings of the Cisco small business router, there weren't really any settings that stood out. It was basically factory default.
- The ISP for this network is Comcast. They have a dynamic IP address because they don't need a static IP. The Cisco small business router just picks up the private IP address issued by the Comcast modem. Pretty much a standard configuration for a dynamic public IP address.
The IP address of the SBS server 2003 is: 10.0.1.5 (
the IP address of the server gateway is: 10.0.1.1
the IP address of the server's Primary DNS is pointed to itself which is: 10.0.1.5 (which I believe is correct when setting up DNS on the SBS 2003 server)
- there is no entry for the secondary DNS server
Under DNSMGMT the DNS Event logs is showing these errors every few minutes. The website in the “ “ would be different websites that perhaps users are accessing. There are hundreds of entries some showing different websites within the quotations
The DNS server encountered a packet addressed to itself on IP address 10.0.1.5. The packet is for the DNS name ".". The packet will be discarded. This condition usually indicates a configuration error.
Check the following areas for possible self-send configuration errors:
1) Forwarders list. (DNS servers should not forward to themselves).
2) Master lists of secondary zones.
3) Notify lists of primary zones.
4) Delegations of subzones. Must not contain NS record for this DNS server unless subzone is also on this server.
5) Root hints
Currently all users can access data on the server and they can successfully connect to the exchange server.
However, I have one other major issue. About a week ago when I swapped out the routers to use the Linksys home router, some users can get to exchange some users couldn't. All PCs on the network are in the domain.
- There is one user has a laptop that's in a workgroup. He can connect to the server's data and exchange when connected to the original router. Now that I have the Linksys home router connected, he cannot connect to any of the map data drives and exchange. The quick fix would be to put the original router back in place. But if I did that the backups fail again.
I am somewhat stuck as to what my next action should be
I think my main concern at this point is. I believe it's DNS related
- what is the minimum and correct settings I should be using in the router?
- is there possibly something wrong that set up and DNS on the server?