Techdivision
asked on
Small Business Server 2008 cannot access Internet
I'm in the middle of migrating from SBS 2003 to 2008. I've set up the new server with the migration wizard. It can be seen on the network (and accessed remotely), and can see other items.
However, it can't access the Internet, and it's the only computer that can't do it. It can ping the default gateway and bring up the router configuration page, and when I ask it to ping www.google.com, it resolves the IP address correctly. However, it can't route outside the network. I've run the Internet connection wizard countless numbers of times, and this is driving me nuts! Anyone with any suggestions?
However, it can't access the Internet, and it's the only computer that can't do it. It can ping the default gateway and bring up the router configuration page, and when I ask it to ping www.google.com, it resolves the IP address correctly. However, it can't route outside the network. I've run the Internet connection wizard countless numbers of times, and this is driving me nuts! Anyone with any suggestions?
How does your internet works? Do you have a HUB, a switch, wireless? Had you configured tou TCP/IP? More information please, about your connections.
ASKER
We have a router, 192.168.51.254. The server has an IP address of 192.168.51.1. Subnet mask is 255.255.255.0. All the other computers on the network can connect to the Internet (15-user network). Default gateway is .254, and although I can ping that, can't ping anything beyond that. If I go onto another computer on the network, and ping www.google.com, I get a response. Likewise, tracert www.google.com doesn't get any further than the .254 gateway.
What OS is it? Have you tried to disable the IPv6? Have you checked all the Ip's to see if there is any conflict? The network is under a domain? Do you know if your DHCP has limited connections number?
ASKER
It's Windows Small Business Server 2008, so it's running a domain. Haven't tried disabling IPv6, but that could be dangerous - there are clients authenticating via this machine. And it does respond, it just doesn't route. I'm trying to avoid putting in something draconian like netsh int ip reset, because it could cause all sorts of knock-on problems with the DHCP server (it IS the DHCP server for the network, btw).
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
DrDave - No, there are no outgoing firewall restrictions. I've checked that.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks guys, it was actually the bloody Cisco SDSL router on the edge that was causing the problems. Rebooting the firewall didn't help, but rebooting the router did. Doh!