Nat Routing

[DCMan]

Hi all

 

I've just done my first full setup of Server 2008. I've managed to get everything working. The client computers log on to the domain, and folder etc redirect successfully. The server has internet access.

 

My problem is coming in trying to get the client computers to access the internet through the server. Its the only server on the network and so its having to act as domain controller, dhcp/DNS etc etc. The clients pick up all the settings fine. Their ips are allocated from the server, they pick up their DNS as the server I am configuring and the default gateway as the one on the network. The external DNS servers that the server connects to are also correct.

 

The server has 2 lan ports, so I am using one which is a direct connection to the internet gateway, and the other one goes to a switch, which the client computers are plugged into. The client computers can ping each other and the server, but not the gateway. The server can ping everything. So I have to come to the conclusion that its the routing between the 2 lan ports..

 

What am I missing?!

 

I'll give you the settings, and you may be able to tell me what to plug into where!

 

 

External DNS1: 62.171.194.104

External DNS2: 62.171.194.105

Server IP: 10.130.189.20

Client DHCP Range: 10.130.189.50 - 10.130.189.200

Gateway: 10.130.189.254

 

 

There will also be a proxy involved at a later date. Where do I need to put the settings for that too!?

 

Any ideas!? Thanks! :)

[F2 Staff]

How do they login?

 

This sounds like it might client side where the problem is coming from.

 

Try

 

tracert -d 74.125.53.99

 

From the client box and lets see what happening. That is Google's IP. Better to start the troubleshooting by IP. If that works then we have a DNS problem.

[DCMan]

I'll have to do that specific IP on monday when I'm back with the server, or if I feel really dedicated (and if I manage to fix my washing machine early enough in the day.. :lol:), I might have a look tomorrow!

 

However, I did try a tracert on a couple if IPs on the network itself. If I do a tracrt to the server itself, it gets an immediate and correct response. If I do a tracert to any other ip on the network, I get destination unreachable.

 

If I do the same test, but pinging, the server obviously replies straight away. If I ping another IP, the request times out, but normally one or two of the responses will be the client computer saying Destination Unreachable.

 

If it is a problem on the client side, then it will be coming from something I have done on the server and what it is allocating to the client. The clients are being assigned everything from the server, if that makes sense? So I'm pretty sure its to do with the routing between the 2 LAN ports on the server - however, I'd be more than happy to be wrong if we can get it sorted!! :lol:

 

Thanks for the reply :)

[DCMan]

Actually, just thinking about it, I didnt try it with the -d switch.. I'll do that as well :)

[F2 Staff]

If the client has the firewall enabled they can't be pinged and you'll get timeout or network unreachable with tracert.

 

When a user logs in to the server how do they log in? RDP? VPN?

 

If I understand you correctly clients can connect to the server. When connected they can't access the internet.

 

Is that correct?

 

Good luck with the washing machine BTW.

[DCMan]

Hi again

 

Well, I fixed it! :lol:

 

Basically, everything was set up right, but I'd forgotten to bridge the 2 connections! Not sure if thats always the conventional way of doing it, but its worked so I'm leaving it!! hehe!

 

If you have any more input, feel free to share, as I'm up for learning still!

 

Now all I have to do it work out how to use it to deploy packages and I'm sorted for now

 

Thanks again!

 

(The washing machine had completely died... but some friends of ours just upgraded their 6 month old machine and randomly offered me their old one! So that was a good outcome too! :lol:)