Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
We updated a sbs 2000 server to sbs 2003. I have went through the to do list for "Connect to the internet". Clients have internet access but sever does not. It appears that the dns only looks at it'self and does not use the forwarders, which are the ISP DNS server addresses. Also a second issue, The clients cannot ping the server. The server can ping the clients, it can ping the default gateway, it can ping it'self. A little network configuration.
server 192.168.0.100 static
default gateway 192.168.0.1
forwarders 65.106.1.196 & 65.106.7.196
only 1 nic
no server firewall
An interresing point
I can ping the default gateway but opening the browser and typing http://192.168.0.1 in the address bar gives "The page can not be displayed"
The isp's dns entries, are they in the forwarder tab or in the forward lookup zone?
what do the clients have for dns entries? Doesn't sound like they are pointed to your dns server but the isps. That is incorrect configuration.
Golly gee wilerkers everyone. Learn to Internet Search
0 
0
If you are using a SOHO router, try setting up forwarding to your router.
Please help survivors of Hurricane Katrina.
www.redcross.org
0
DNS is configured correctly then and we are not dealing with a dns issue.
What is throwing me is that fact with this proper config your workstations can get to the web and don't have name resolution issues.
My first thought is to swap out the nic and cable but it appears they are working correctly or when dns forwards a workstation request for like google.com it wouldn't work.
Clearly the wksts can resolve google and get to the server so the hardware can't be the issue.
Starting to look like corrupt Internet Explorer on the server. Look at the security settings in IE
Golly gee wilerkers everyone. Learn to Internet Search
0
I agree, It does not make sense. IE is a posibility. Any way to uninstall/reinstall? We have a DC on this server and also web services, I am also thinking about formatting and then a clean reinstall. We have done repair install with no luck.
0
I tried sfc /scannow did not help. I tried netsh winsock reset command, no help. I downloaded on a client, the firefox browser, moved to server and installed. Now have internet. Issue is with IE.
0
Well I did another repair install and ping and IE are working . Go figure!!!! One final question. Do i need to put the sever IP into the dns primary in the router. So when clients connect they will get this dns address?
0
Hey great to hear! Bet firefox nudged MS in the right direction. :-)
don't put the 03 server dns address in the router. Wksts are resolving by going to 03 dns and 03 dns is taking care of the rest. That's how MS designed it.
Golly gee wilerkers everyone. Learn to Internet Search
0
Opps! I just realized you are doing dhcp from the router not the server.
You want to do dhcp from the server not the router for the workstations. With DDNS DHCP dynamically updates microsoft's dns.
Highly advise you provide dhcp from the server not the router as per MS design.
Golly gee wilerkers everyone. Learn to Internet Search
0  |
 |
 |
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
