Windows Forum

Ask something
Discussion Locked

NT routing troubles #2

0 helpful
9 replies

by razorren

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have a NT 4.0 server connected to the internet via cable modem.One network card ip 192.168.24.1 is connected to my internal network, the second nic with ip 208.x.x.x is connected to the internet. I have ip fowarding turned on and from a NT workstation I can ping the external interface of my NT server, but I can't ping my isp or anything else. How can I set it up so I can foward all of the traffic on my local lan or from my proxy server for the internet to my NT server.

9 replies

by -dag

It sounds like your problem is that the 192.168.x.x address is not routable. You will have to use NAT (network address translation) to accomplish this as you have a fully qualified external IP address and a private, non-routable address inside.

by stillatit

You have the hardware set up. Now install Proxy Server software, which will accept requests from your stations on your LAN and use its 208... address to do the internet access and pipe the answers back to the LAN stations.

Alternative: Put a router with NAT (Network Address Translation) where the NT server is, take one NIC out of the server, and put it on the LAN with the workstations. I personally like the Netgear RT311 or RT314 routers, since they will spoof the MAC address of the station which the cable company registered (the 208 NIC on your NT box), so that you do not have to have the cable company make any changes.

Good luck.

by simonsia

Your problem is definately with the NAT. I suggest the following 3 ways in the order of ease:-
1. Use Windows 2000, and configure NAT using the 'Routing & Remote Access". Configure one NIC as public and another NIC as private. Make sure you enable the NAT, and enter the private address as a DHCP server. Everything should be automated, as long as your workstation is on the network.

2. Use Netgear or equivalent router to setup the NAT. Your server then will be behind the router with private address.

3. Considering you still using NT4.0. Microsoft Proxy Server probably is the best way to go. I put this as the last option is because I think Proxy Server is harder to troubleshoot in the case of a problem.

Good Luck
Simon Sia

by pherra

I agree with the previous replies, NAT is the way to go. I just wanted to add...Your current setup is full of security leaks and I would remind you that if someone hacks into that machine they will have full run of your private network.

This discussion is closed to new replies.