Pick Your Brains - 2k Server

Exon · Post #1 (**permalink**) 03-10-2005, 09:18 AM

Alright here's the layout.

Windows 2000 Server. NAT enabled and assigning a 192.168.0.x scheme.
The server (We'll call "Hulk") has a dynamic External IP of 12.217.187.x and a static Internal IP of 192.168.0.1 - of which it is connected to the switch and assigns the IPs.

Clients can obtain an IP, ping each other, ping the server - but are unable to get to websites, check E-mail, or ping External IPs.

Hulk is able to ping everyone, get to websites, check E-mail, and ping External IPs.

Why aren't clients able to get to the internet - but are able to get an IP?

Screenshots can be provided if needed.

*Brain Burnt Out*

layerblue · Post #2 (**permalink**) 03-10-2005, 09:48 AM

You need to setup routing on that server, if you are trying to use it as a gateway. People will get an IP address because DHCP is enabled, but they won't be able to route through the W2K box because it's not setup to act as a gateway.

Exon · Post #3 (**permalink**) 03-10-2005, 09:53 AM

Routing and remote access is setup, if by setup you mean configured and enabled?

Exon · Post #4 (**permalink**) 03-10-2005, 10:51 AM

Fixed.
Routing And Remote Access --> SERVER NAME --> IP Routing --> NAT Properties --> Name Resolution --> Client Using DNS.

*slaps self*

Okie. Done - fixed - now to run it offsite and see if it connects to the Parent Domain Controller like a good little Child DC should.

layerblue · Post #5 (**permalink**) 03-10-2005, 05:22 PM

Well, at least I got ya pointed in the right direction

Exon · Post #6 (**permalink**) 03-10-2005, 07:46 PM

Yes - and I thank ya for that.

kysales · Post #7 (**permalink**) 06-03-2005, 02:03 AM

The solution is very simple

Open the networking properties on the network card in the server

in the name servers second it gives you 2 coices to put name server ip address's

Most people simply put the ip's of the name servers provided by their isp.

To solve your problem, get an ip address of anyones name server that is not on your network, it doesn't matter where

put that ip in the name server slot for the second name server and your clients will now have access to the web, leave the first name server ip what you were provided by your isp

The simple answer is that your server needs an outside source to get propergation to outsite websites.

MOD NOTE: Post edited. Self-promotion is only allowed in the Hosting Discussion MarketPlace.

webfreak08 · Post #8 (**permalink**) 06-03-2005, 04:21 AM

MOD NOTE: kysales, please set up a signature in your User CP and do not manually add your website to your posts. Furthermore, follow all forum rules when posting. Thank you.

Exon · Post #9 (**permalink**) 06-03-2005, 07:17 AM

Thanks kysales, but I got it working.

TRau · Post #10 (**permalink**) 06-03-2005, 12:51 PM

kysales,

The proper way to do what you discribed is to have one of your DNS servers forward to the ISP DNS server(s). All devices on your network (including servers) should point to your DNS server, not any outside ones. Otherwise things slow to a crawl.