Discussion Locked

Using NT Machine as Router

0 helpful
33 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I know this is possible but I am missing something.

Lets say I have 3-win9x clients, 1-NT PDC, 1-10Mb hub and 1-100Mb hub. Accepting that the hubs cannot be cascaded, I want to turn my NT machine into a "gateway/router" to do it for me.In 2f the win9x machines, I have a 3Com 3C905 10/100Mb NICs. In the other win9x machine, I have a 3Com 3C509B 10Mb NIC. In the NT machine, I have 1 of each. I assume that I need to have 2 separate subnets defined for the different segments so I am using 19.168.1.xxx on my 10Mb segment and 192.168.2.xxx on my 100Mb segment.

The IP address of the server is 192.168.1.100 for the 10Mb and 192.168.2.100 for the 100Mb. The NT machine has IP forwarding, DNS resolution, and WINS services active and started wth no errors. Each of the win9x machines have their default gateways for their NIC pointed to the NIC that they match in the NT machine. The 100Mb segment can see all of the machines on its segment as well as the NT machine. The 10Mb side can see all o

33 replies

by slacker

You need to build the "Local Address Tables" for each NIC. In the protocol control panel for each NIC add all of the addresses for both sides of the network.
It may help to build an lmhosts file that includes all of the IP's as well and drop it into the:\Windows directory on each of the machines. The end of your question was cut off, but that is how I am doing something very similar.

by daniel

Have you built a routing table at the server? Use "Start"-"Run"-"cmd" on the server console to invoke a DOS-session. Use "route -p ADD 192.168.1.0 MASK 255.255.255.0 192.168.1.100 METRIC 1" and "route -p ADD 192.168.2.0 MASK 255.255.255.0 192.168.2.100 MERIC 1" to add the new routes as persistent ones. The syntax of route used in this example is route -p ADD Destination MASK SubnetMask Gateway METRIC HopCount. You can get more help by typing "route /?" at the DOS-Prompt.

Another way that I wouldn't useis to use regedt32 to edit the key HKLM\System\CurrentControlSet\Services\Tcpip\Parameters\PersistentRoutes. Data type is REG_SZ, data format is comma-delimited Destination,SubnetMask,Gateway,PrimaryRouteMetric with no spaces inbetween. But be aware thatanipulating the registry carelessly may damage your system seriously!!!

Hope, I could help you

Daniel

by Former member

You can also just set the default gateway on each card in the NT machine to the other card. This works when you only have two cards and it is simple and quick to set up. It will let you access the two networks. Not as robust as building the tables thouht

by abbot23

fIRST:U need to verify that all computer are on one subnet mask/255.255.255.0 or something/ If u use diff submasks all computers will see each other only if they are on one submask/encrised security/
2: Make sure that gateways are correct : on 10mbgatewy is NT ipadres, on 100mb gateway is youre real gateway
3:Check DNS - on nt yore is working, but if u have one somewhere else and NT is uses it and u set another one on ure nT may this is the problem!/start IExplorer on clients and try WWW adres - if retrn a DNS lookup failure - u get it ;))/
4.chek ip adresses by ping - if they are from DHCP/obtain automatikali/ and u use one twice - this is error! use the same DHCP server everywhere! Thats all, folks! :-))

by fremen

Find out and install RRAS ("Routing Remote Access Service") from Microsoft.
Then with the new RRAS Manager configure your Routing Tables. If you don't know how, follow the instruction in the help files provided by Microsoft. Remeber to install first SP3hen RRAS and then SP5.
If you need more help contact me ...

by s_tabak

This is simple and try this first.
set up both network cards to work properly with its own network then share the network card and set the permissions the way you want it.

by slav

In options of NIC's tcp IP take care to provide both of them ( on server - router) with next gateways:

gateway of 192.168.2.100 : points to 192.168.1.100
gateway of 192.168.1.100 : points to 192.168.1.xxx where xxx is adress of 10mb win95 machine
Iassume that 192.168.1.____ is 10mb segment
all the others 100mb NICs must have gateways 192.168.2.100

The seocond solution is to live server away of this duty. Give this task to one of the win95 machine. Put on it the two NICs 10mb an 100mb then givethem proper adresses for example:
IP 192.168.2.101(100mb)gateway192.168.2.100
IP 192.168.1.101(10mb) gateway192.168.2.101
In this case one win95 10mb NIC left alone will have IP adres for example:
IP 192.168.1.102 (10mb)gateway192.168.1.101

I'veade this tree times sucsessfully.

by ricky.l.schultz

I have also done this with many NT machines using isolated sub-nets. For example one card to the world the other to a test bench only. I have found that I have to eliminate the default gateway entry for the card on the Isolated side. NOT the side tothe wrld where WINS or DHCP or DNS are being supplied from. For some reason NT refuses the entry and bottles up I/O on both cards.

Thus You can enter the Gateway into router table (THE REAL ROUTER) and then access anything on the isolated subnet side throug the NT box acting as a router.

Hope that helps

by mgardner

Spend the $50.00 on a 4 port dual speed hub, and use that to connect the other 2 hubs together. That way, they are all on the same subnet, you do not have to blow cpu cycles on making NT a router, and you save the time needed to administer your routing table.

by muellert

Remove the NIC from the 19.168.1.xxx segment machine. Install a 10/100 card and place in on the 19.168.2.xxx segment. This is cheap and quick to do and puts all your clients on a 100 mbit segment. (simple)

by the panda man

I understand what you are trying to do here, using NT as a router/slave-port is like trying to use a mountian to hold down a peice of paper. Somewhat overkill. You might have a bit better luck with 95/98 archetecture. But since you have gone threw all this trouble to develope and set up this network, lets see.
Windows NT is a very picky operating system. Picky from the standpoint of, it only like certian hardware in certian configurations. From your question, it sounds like NT is having trouble seeing one of your nodes. You may wish to first check on the Microsoft Site, under support, the NT hardware compatability list. This list is updated daily and lists everything that NT will communicate with. If you have trouble finding it, check my Bio andsend me an EMail, I will send you a link to get in. If hardware compatability proves not to be the answer, try to redefine your configuration, assign your faster network card as the first in line to be addressed, create your routing table and assign each

by fschuurman

Oke, technically everything works per net. (why didn't you used a crosscable to attach the 10Mb on the 100? just a thought). Can you ping all the computers from the NT host. This should be your nex step. When you can ping them try ping from a w95 the def. router card. (f.i. x.x.2.100) then the other card (f.i. x.x.1.100). If this works, routing is oke and you have a other problem (maybe local on client). If this doesn't works try to add the routes. The table (route print) should show at least the following:

127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
192.168.1.0 255.255.255.0 192.168.1.100 192.168.1.100
192.168.2.0 255.255.255.0 192.168.2.100 192.168.2.100

Please pay attention to the broadcast adresses x.x.x.255 with 255.255.255.255 subnetmask and that all you're clients have the same subnet as displayed in the table (255.255.255.0).

Good Luck.

Additional the URL for the RRAS mentioned earlier: http://www.microsoft.com/ntserver/nts/downloads/winfeatures/rras/rrasdown.asp

by copes_r

All you have to do is adjust the default gateways. The 100mg card adress(192.168.2.100) should be the default gateway for the 10mg network, and vice versa. I have done this to connect a tokenring with an ethernet, so your should be the same.
If you aregoing to get much bigger with this, though, I would recommend installing a switch. They are fairly cheap. and they connect through hardware, which would be faster. This would also free up the PDC resources. hope this helps,
-Rick

by jim beall (a.k.a. jbeall a.k.a. reflexis)

The steps for routing with NT:
- Install TCP/IP and make sure that it is bound to both network cards.
- assign the card connected to the 192.168.1.0 network an address of 192.168.2.100 and a subnet mask of 255.255.255.0 default gateway 192.168.2.100
-assign the NIC on the 192.168.2.0 network the address of 192.168.2.100 subnet mask 255.255.255.0 and leave the default gateway blank
- under the routing tab of TCP/IP properties make sure that the enable IP forwarding is enabled
- go to start/programs/command prompt
- type in route add -p 192.168.2.0 255.255.255.0 192.168.1.100 press return
- type in route add 192.168.1.0 255.255.255.0 192.168.2.100 press return
- now you should be configured to route between the two subnets. I shouldnote that if you have a internet connection (i.e. a isdn router) then the default gateway should be that device's ip address not the other NIC
hope this helps.
Jim

by lim_tecksheng

You need to make sure that the NT Server is able to see both networks as a persistent route using the route add command:

route -p ADD 192.168.1.0 MASK 255.255.255.0 192.168.1.100
route -p ADD 192.168.2.0 MASK 255.255.255.0 192.168.2.100

You can use netstat -rn to check that the routes have been added. Once you have added this in, you'll need to enable the RIP (Routing Information Protocol) Service by going into the network properties dialog and adding the service onto the server ie.
1. Get into the Network Properties dialog(right click on Network Neighbourhood and select the item)
2. Click on the Service tab
3. Click the Add button
4. Select RIP
etc.etc. to install
(Note: This service is not added by default)

I encountered the same situation months ago and this was the only way I could get it to work. I tried using static routes on the server for a few machines on each network segment without enabling RIP and it didn't work for me. You will need to enable RIP for the static route of the su

This discussion is closed to new replies.