Configuring NT Server to be a router
Hoang Do
Does anyone know the way to configure an NT Server to act as a router
with two NIC cards? I'm looking for the procedure to do this and possibly
whatever settings necessary to set the server up to behave like a router
by propagating packets it sees from one NIC to the other. This is for a
TCP/IP network.
thanks,
Hoang
hoa...@earthlink.net
Nancy Curtis
I think all you have to do is install separate IP addresses on each card.
Then plug in the correct segment of the network cable.
Hoang Do <hoa...@earthlink.net> wrote in article
<5cnn7j$k...@chile.earthlink.net>...
Mike taylor
Below is correct but make sure if you break the nics apart into subnets and
then make route add statments.
Nancy Curtis <ncu...@zd.com> wrote in article
<01bc0e0c$1bfc0970$1168289b@ncurtis>...
Mikkel Brodersen
Search www.microsoft.com for tcpipnt.doc
It's a document titled "Advanced Internetworking with TCP/IP on
Windows NT" with an excellent explanation of the required steps you
should take.
Best Regards
Mikkel Brodersen, Olicom A/S, Denmark
On 29 Jan 1997 14:35:31 GMT, hoa...@earthlink.net (Hoang Do) wrote:
>Does anyone know the way to configure an NT Server to act as a router
>with two NIC cards? I'm looking for the procedure to do this and possibly
>whatever settings necessary to set the server up to behave like a router
>by propagating packets it sees from one NIC to the other. This is for a
>TCP/IP network.
>
>thanks,
>
>Hoang
>hoa...@earthlink.net
>
---------------------------------------------------
Mikkel Brodersen Olicom A/S
Product Manager Nybrovej 114
e-Mail: m...@olicom.dk DK-2800 Lyngby
WWW: www.olicom.dk DENMARK
Fax: +45 45270300 Tlf: +45 45270094
---------------------------------------------------
Hoang Do
In article <ORaQQXAx...@psp.co.uk>, t...@psp.co.uk says...
>
>x-no-archive: yes
>In article <01bc0e0c$1bfc0970$1168289b@ncurtis>, Nancy Curtis
><ncu...@zd.com> writes
>>I think all you have to do is install separate IP addresses on each card.
>>Then plug in the correct segment of the network cable.
>
>look upder protocols/tcp ip
>
>
Funny, I did all of the above and it didn't seem to work. Each machine on
different segments can see the server; the server can see both machines, but
the machines on different segments can't see each other. I tried the advice
given that you should put the IP for each NIC to be default gateways to each
other. This causes NT to route..? makes sense, but it didn't work either.
My configuration is as follows:
----------------------
| NT Server |
NIC 1 ---------------------- NIC 2
IP: 15.15.2.1 | | IP: 15.15.1.1
Submask:255.255.255.0 | | Submask:255.255.255.0
Def.Gateway:15.15.1.1 | |Def Gatewy:15.15.2.1
|---------------------------| |---------------------------|
| |
Win95 WinNT Workstation
15.15.2.2 15.15.1.2
255.255.255.0 255.255.255.0
Def Gatewy:15.15.2.1 Def Gatewy:15.15.1.1
Hoang
hoa...@earthlink.net
Mikael Storsjo
Set the Default Gateway for NIC 2 to nothing (not 0.0.0.0). I have read
in the newsgroups that this should solve your problem.
R. Van Valkenburgh
I remember that there is a registry change that you need to make; but
I can't remember what it is ir where I saw it. If you do not make
that change then it will work as you indicate your is.
John
# >In article <01bc0e0c$1bfc0970$1168289b@ncurtis>, Nancy Curtis
# ><ncu...@zd.com> writes
# >>I think all you have to do is install separate IP addresses on each card.
# >>Then plug in the correct segment of the network cable.
# >
# >You also have to enable IP Routing In control panel/networks
# >look upder protocols/tcp ip
# >
# >
# Funny, I did all of the above and it didn't seem to work. Each machine on
# different segments can see the server; the server can see both machines, but
# the machines on different segments can't see each other. I tried the advice
# given that you should put the IP for each NIC to be default gateways to each
# other. This causes NT to route..? makes sense, but it didn't work either.
#
It may make sense, but it's wrong. The gateway field for the second card
should be blank; the gateway for the first card should be the real gateway.
--John
Ben Hannon
Did the search can't find this document, seems to be missing?
anyone know where it is?
Thanks
Mikkel Brodersen <m...@olicom.dk> wrote in article
<32f09020...@olicom.olicom.dk>...
Ivan Rojas
- Ok. What happens if you have on NIC 2 a router to a ISP ? Should be the same, def. gw 0.0.0.0 in NIC1 and real gw on NIC2 ?
- ********************************************
- Ivan Rojas Liikkuva Systems Intl.
- R&D Engineer iro...@liikkuva.com
Carl Wagner
At 15.15.2.2 add this route command:
ROUTE ADD 15.15.1.0 MASK 255.255.255.0 15.15.2.1
This command will have to be executed after every boot for WIN95 clients.
At 15.15.1.2 add this route command
ROUTE -p ADD 15.15..2.0 MASK 255.255.255.0 15.15.1.1
This command with the -p option become persistant on NT machines and need
not be entered again.
--
Carl Wagner - LAN Admin
Morrison Health Care, Inc.
Mobile, AL, US
R. Van Valkenburgh <van...@auburn.campus.MCI.net> wrote in article
<32f0ffdd....@news.campus.mci.net>...
> I remember that there is a registry change that you need to make; but
> I can't remember what it is ir where I saw it. If you do not make
> that change then it will work as you indicate your is.
>
> hoa...@earthlink.net (Hoang Do) wrote:
>
> >In article <ORaQQXAx...@psp.co.uk>, t...@psp.co.uk says...
> >>
> >>x-no-archive: yes
> >>In article <01bc0e0c$1bfc0970$1168289b@ncurtis>, Nancy Curtis
> >><ncu...@zd.com> writes
> >>>I think all you have to do is install separate IP addresses on each
card.
> >>>Then plug in the correct segment of the network cable.
> >>
> >>You also have to enable IP Routing In control panel/networks
> >>look upder protocols/tcp ip
> >>
> >>
> >Funny, I did all of the above and it didn't seem to work. Each machine
on
> >different segments can see the server; the server can see both machines,
but
> >the machines on different segments can't see each other. I tried the
advice
> >given that you should put the IP for each NIC to be default gateways to
each
> >other. This causes NT to route..? makes sense, but it didn't work
either.
> >
Michael Haley (mhaley at scope dot com)
Thomas Lee wrote:
> >My configuration is as follows:
> >
> > ----------------------
> > | NT Server |
> > NIC 1 ---------------------- NIC 2
> > IP: 15.15.2.1 | | IP: 15.15.1.1
> > Submask:255.255.255.0 | | Submask:255.255.255.0
> > |---------------------------| |---------------------------|
> > | |
> > Win95 WinNT Workstation
> > 15.15.2.2 15.15.1.2
> > 255.255.255.0 255.255.255.0
> > Def Gatewy:15.15.2.1 Def Gatewy:15.15.1.1
>
> gateway. And in any event, a gateway must always be 'local' to the
> subnet: 15.15.1.1 is not on the same subnet as 15.15.2.1 thus is an
> invalid gateway.
This sounds like hooey. I think you have the right idea maybe, but it's
like this:
A gateway must be on and have the same subnet address as all hosts which
use the gateway. A multi-homed machine configured as a router acts as
gateways to more than one subnet. It forwards packets from one subnet
to another whenever necessary.
If 15.15.2.2 wants to communicate with 15.15.1.2, it recognizes that the
destination has a foreign subnet, and sends the IP packet inside an
ethernet (or token-ring, etc.) packet addressed to the gateway
15.15.2.1. The gateway then also recognizes that the packet needs to be
forwarded, consults its routing tables, and forwards the packet
15.15.1.1, the gateway needed to reach 15.15.1.2. That gateway then
forwards the packet to 15.15.1.1 directly. Return packets follow the
opposite route.
Mikael Storsjö
Hoang Do <hoa...@earthlink.net> wrote in article
<5cnn7j$k...@chile.earthlink.net>...
> Does anyone know the way to configure an NT Server to act as a router
> with two NIC cards? I'm looking for the procedure to do this and
possibly
In the Knowledge base on www.microsoft.com you find this document:
"How To Configure Windows NT as a Remote IP Router"
Article ID: Q123024
William L. Whipple
You are falling victim to a common misconception: When you define a default
gateway on an NT system it applies to the system, not to the interface. The
way MS built the GUI is very misleading, but if you do a ROUTE PRINT you will
get a better picture. There is just one routing table for the system, not one
for each interface.
Also, if you are not going to set a default gateway in the MS GUI for an
interface, set the entry to blanks, not zeroes.
--
=============================================
William L. Whipple - Network & Internet Consulting
HTTP://WWW.WLW.Com/ - Bill.W...@WLW.Com
HTTP://WWW.EZine.Com/ - Information of the Net
Ivan Rojas <iro...@liikkuva.com> wrote in article
<32F26C...@liikkuva.com>...
William L. Whipple
Unless this net is linked to something else, the NT system used as a router
does not need and should not have default routes - leave them blank. By adding
the IP address and netmask for each of the interfaces, you are giving NT all
the information it needs to find the two network segments. Set the IP
Forwarding setting to Enabled and it should work.
The client systems do need to have a default gateway that points to the NIC on
the NT router that is on their segment, and it looks like that is what you are
doing.
You might try going to the command prompt on one of the client systems and
doing a TRACERT to an IP address of a system on the other segment. The first
hop should be the NT router system, and the second hop should be the
destination system.
If it doesn't work, what version and service pack on NT are you using?
--
=============================================
William L. Whipple - Network & Internet Consulting
HTTP://WWW.WLW.Com/ - Bill.W...@WLW.Com
HTTP://WWW.EZine.Com/ - Information of the Net
Hoang Do <hoa...@earthlink.net> wrote in article
<5cq7go$d...@uruguay.earthlink.net>...
> In article <ORaQQXAx...@psp.co.uk>, t...@psp.co.uk says...
> >
> >x-no-archive: yes
> >In article <01bc0e0c$1bfc0970$1168289b@ncurtis>, Nancy Curtis
> ><ncu...@zd.com> writes
> >>I think all you have to do is install separate IP addresses on each card.
> >>Then plug in the correct segment of the network cable.
> >
> >You also have to enable IP Routing In control panel/networks
> >look upder protocols/tcp ip
> >
> >
> Funny, I did all of the above and it didn't seem to work. Each machine on
> different segments can see the server; the server can see both machines, but
> the machines on different segments can't see each other. I tried the advice
> given that you should put the IP for each NIC to be default gateways to each
> other. This causes NT to route..? makes sense, but it didn't work either.
>
> My configuration is as follows:
>
> ----------------------
> | NT Server |
> NIC 1 ---------------------- NIC 2
> IP: 15.15.2.1 | | IP: 15.15.1.1
> Submask:255.255.255.0 | | Submask:255.255.255.0
> Def.Gateway:15.15.1.1 | |Def Gatewy:15.15.2.1
> |---------------------------| |---------------------------|
> | |
> Win95 WinNT Workstation
> 15.15.2.2 15.15.1.2
> 255.255.255.0 255.255.255.0
> Def Gatewy:15.15.2.1 Def Gatewy:15.15.1.1
>
>
> Hoang
> hoa...@earthlink.net
>
>
>
>
Jim Hockin, Santa Barbara
You have to remember that when you have one "Multihomed" computer (two
nics) serving two subnets, you keep each default gateway within it's own
subnet. Those Microsoft instructions that appear to be swapping default
gateways is for when you have two "Multihomed" computers acting as
routers serving up to three subnets (thats four nics total in two
multihomed machines). That's when each multihomed computer can have the
address of the other multihomed computer as a static route for its
default gateway and rout between each other with no other configuration
necessary. MS is quick to point out, though, that this only works
effectively with two routers. Any more requires manually adding an entry
in the routing table.
jph
Plattner Christoph
Hoang Do wrote:
>
> Does anyone know the way to configure an NT Server to act as a router
> with two NIC cards? I'm looking for the procedure to do this and possibly
> by propagating packets it sees from one NIC to the other. This is for a
> TCP/IP network.
>
> thanks,
>
> Hoang
> hoa...@earthlink.net
Hi !!!
Ever heart about RIP a self-learning router, it
can be installed on NT 4.0 Server with the icon
"Network" in the "Control Panel". I have no
experience, but I think it can help you !!!
John R Buchan
In article <33016F...@ict.tuwien.ac.at>, plat...@ict.tuwien.ac.at says...
RIP will only help, if there is another RIP aware router attached to
one of the segments. IF this is a simple 2 segment LAN, as the post
seems to indicate, then it should require nothing beyond proper IP
configuration (eg, each segment ona different subnet) and enabling
IP forwarding on the router.
The tech section of www.ezine.com has some useful info on this.
--
John R Buchan Independent Consultant Orlando, Florida USA
MCSE -++- MVP ...................... j.bu...@worldnet.att.net
Gilles Chamberland
In the WinNT 4.0 Server Ressources kit, in the ONLINE documentation
section, there is a WRI file that explains the routing under WinNT 4.0.
It should help you.
Gilles C.
John R Buchan <j.bu...@worldnet.att.net> wrote in article
<5dtp33$p...@mtinsc05.worldnet.att.net>...
Peter Fry
Gilles Chamberland wrote:
>
> In the WinNT 4.0 Server Ressources kit, in the ONLINE documentation
> section, there is a WRI file that explains the routing under WinNT 4.0.
I can't resist such a massive crosspost...
How about RAS to LAN? I'm talking experience here, not quotes from
the Resource Kit (unless you've found it to work as presented).
I haven't spent much time at it, but I did try the registry mods
recommended for 3.51, to no avail. The routes were there -- NT just
ignored them.
Oddly enough (referring to the original subject) I've had no problems
routing LAN to LAN.
Peter E. Fry
J. Brosterhues
Hi,
you won't need any RIP stuff to solve the problem. RIP is used to exchange
routing tables between several routers.
Just go into TCP/IP properties to enable IP routing using the appropriate
tab (NT 4.0 = Routing tab, NT 3.51 = routing checkbox).
This will do the job.
Plattner Christoph <plat...@ict.tuwien.ac.at> schrieb im Beitrag
<33016F...@ict.tuwien.ac.at>...
Keith Knostman
Hi J,
I am having the same problem getting routing to work between two cards
in NT server for my LAN. I need to know how to configure not only the
server but also the other machines on the lan to rout through one card
on the lan in the server through the other card to my ISDN router. For
example, what gateway should the clients point to? Should they point to
the router or the server? What should the two cards point to in the NT
machine? The LAn card? The router card? How should I configure my
subnet masks? Should they change when spliting the IP's between two lan
segments (two cards)?
Hope you or someone can answer these questions and or point me some
where to get the info,
Thanks!
P.S. Please reply via e-mail as well.
Keith knostman
kei...@mcore.com
Benjamin Lau
Try the book "Networking Windows NT 4.0 - Workstation and Server"
from Wiley Computer Publishing (ISBN 0-471-17502-1). It goes for
a listed price of $34.95US and contains just a wealth of
information. You can also check it out at www.wiley.com/compbooks
or at www.winmg.com/netnt. It's not the resource kit but it does
explain a lot.....
Good Luck
-Ben
Keith Knostman <kei...@mcore.com> wrote in article <330B8A...@mcore.com>...
> Hi J,
>
> I am having the same problem getting routing to work between two cards
> in NT server for my LAN. I need to know how to configure not only the
> server but also the other machines on the lan to rout through one card
> on the lan in the server through the other card to my ISDN router. For
> example, what gateway should the clients point to? Should they point to
> the router or the server? What should the two cards point to in the NT
> machine? The LAn card? The router card? How should I configure my
> subnet masks? Should they change when spliting the IP's between two lan
> segments (two cards)?
>
> Hope you or someone can answer these questions and or point me some
> where to get the info,
(snipe...snipe)
Dariusz Korzun
Keith Knostman <kei...@mcore.com> wrote in article
<330B8A...@mcore.com>...
> Hi J,
>
> I am having the same problem getting routing to work between two cards
> in NT server for my LAN. I need to know how to configure not only the
> server but also the other machines on the lan to rout through one card
> on the lan in the server through the other card to my ISDN router. For
> example, what gateway should the clients point to? Should they point to
> the router or the server? What should the two cards point to in the NT
> machine? The LAn card? The router card? How should I configure my
> subnet masks? Should they change when spliting the IP's between two lan
> segments (two cards)?
>
> Hope you or someone can answer these questions and or point me some
> where to get the info,
>
Commonly the problem lays on configuring default gateway for NIC's. You
should use only one default gateway on one NIC.
Chris Corless
Sorry, still no answer, I too am having problems setting this same thing
up. I have an NT 3.51 server with SP4 installed. The server has an
ethernet and token ring adapter installed with IP bound to both.
I have set the machine up exactly as detailed in knowledgebase article
Q123024 (how to configure windows NT as an IP router) but still no luck.
The ethernet side is using IP address 193.119.18.19 with no default
gateway specified and the token ring side uses address 149.82.163.100
with a default gateway of 149.82.163.10. I have checked the IP routing
setting within network setup.
The NT box can ping quite happily anything on either network.
To test the routing I have manually added via the route command a static
route to the 193.119.18.0 network with 149.82.163.100 as the gateway onto
a Win95 machine. With this added I can ping the ethernet IP address of
the NT box. If I try and ping anything else on that network it just times
out. TRACERT shows me getting to the 149.82.163.100 address but then no
further.
This really is driving me crazy so any suggestions anyone has would be
greatly appreciated. Please reply by e-mail as well.
Thanks,
Chris Corless.
Caesar wrote:
>
> Dariusz Korzun (da...@infonet.pl) wrote:
> : Keith Knostman <kei...@mcore.com> wrote in article
> : <330B8A...@mcore.com>...
> : > Hi J,
> : >
> : > I am having the same problem getting routing to work between two cards
> : > in NT server for my LAN. I need to know how to configure not only the
> : > server but also the other machines on the lan to rout through one card
> : > on the lan in the server through the other card to my ISDN router. For
> : > example, what gateway should the clients point to? Should they point to
> : > the router or the server? What should the two cards point to in the NT
> : > machine? The LAn card? The router card? How should I configure my
> : > subnet masks? Should they change when spliting the IP's between two lan
> : > segments (two cards)?
> : >
>
> INTERNET
> |
> |
> ISDN (192.168.1.254/30)
> |
> |
> NT Server Outside Interface(192.168.1.253, mask 255.255.255.252,
> Gateway 192.168.1.254)
>
> NT Server Inside Interface(192.168.2.1, mask 255.255.255.0,
> Gateway BLANK)
> |
> |
> Network (192.168.2.2-254, netmask 255.255.255.0 gateway
> 192.168.2.1)
>
> Your NT Server's outside interface should point to the ISDN router.
> Routing should be enabled in the Control Panel. The inside interface
> should be on a separate subnet from the outside one, and it should NOT have
> a default gateway. The machines on the network should be on the same
> subnet as the inside interface of the NT Server, and should use the inside
> interface's address as their default gateways.
>
> --
> William S. Duncanson
> wil...@neosoft.com
> NeoSoft Operations
> (888) NEOSOFT or (713) 968-5800
Chris McCauley
Chris
I spent ages bashing my head against a wall with a smiliar problem. In my
case I was using two NT servers connected via a microwave link to bridge
two buildings. I eventually got it to work when I realised that I had to
partition the network with the correct netmasks. I ended up with two
"real" subnets on either side of the NT servers. Can't offer any real help
with your problem but I experienced the same sort of problems; able to
ping upto but not across one of the servers etc...
Good luck.
Chris
Marc Houde
Chris Corless <chr...@atm.com> wrote in article <33122B...@atm.com>...
> The ethernet side is using IP address 193.119.18.19 with no default
> gateway specified and the token ring side uses address 149.82.163.100
> with a default gateway of 149.82.163.10. I have checked the IP routing
> setting within network setup.
>
Chris, maybe I'm forgetting something from my TCP/IP days but why doesn't
your ethernet side have a default gateway specified? How is that side
suppose to know where to route?
Marc Houde
Chris Corless
This is how I did it.....
I have an NT 3.51 server with a token ring and ethernet card installed, IP
bound to both cards. The two cards connected to different network addresses
so I didn't have to worry about breaking up a group of addresses.
1. For information on breaking up addresses check out
http://www.ezine.com/EZInternet.SubNet.html
2. For the set-up of the server take a look at knowledge base article
Q123024, this shows you what to configure as far as where to point gateways
on the server itself. Note:- make sure you read the last paragraph about
adding a static route to the router.
3. The clients need to have a default gateway defined which points to the
NIC that doesn't connect to the router. See diagram:-
Win NT Server
----------------------------------------------------------------------------
---------------------
|
|
NIC1
NIC2
a.b.c.1
d.e.f.1
| |
| |
Clients d.e.f.2 (router)
As per the knowledgebase article do not define a default gateway for NIC1,
for NIC2 define a default gateway of d.e.f.2 (the router address). On the
client machines define a default gateway address of a.b.c.1, if you have
any clients on the NIC2 side they need the address of the router as their
default gateway.
This works for me, some other references I found useful were:-
http://www.ezine.com/IPRouting.html#example
Hope this helps you out,
Chris.
J. Brosterhues <jbro...@lanworks.de> wrote in article
<01bc1e93$efdcc4e0$cc9a4dc2@petra>...
Chris Corless
Marc Houde wrote:
> >
> Chris, maybe I'm forgetting something from my TCP/IP days but why doesn't
> your ethernet side have a default gateway specified? How is that side
> suppose to know where to route?
>
> Marc Houde
Hi Marc,
The ethernet side (isolated) picks its routes up from the routes that the
token ring (connected) side knows about.
Chris.
mhi...@home.com
Exactly,
Now that this routing is working, how about a DNS question?
My classic multihomed NT 4.0 router connects two subnets. On the
inside subnet I am using reserved class C addresses (192.168.x.x). I
installed Catapult (Winsock and Web proxy) which also handles address
translation.
The question is, where do I point my internal clients for DNS? The
external interface lists 2 DNS servers. DNS works fine locally on the
server. But NO GO on the other clients.
Thanks in advance,
Matt Hickey
mhi...@home.com
On Tue, 25 Feb 1997 02:11:50 -0800, "Chris Corless" <chr...@atm.com>
wrote:
Ted Kaczmarek
Ted
Todd Webb
Chris,
A couple of things you will need to do. The clients on the TR side need to
point to the NT NIC on their side as DG or if they are pointed to another
router that router needs a static route for the 193.119.18.x subnet.
You would need the same thing on the other side.
Also, NT 4.0 is capable of RIP v1 which will automatilly share it's routes
with your other router if it is configured for RIP v1. MS will have a RIP
v2 and OSPF v2 product out later this year.
Todd Webb
tod...@flash.net
Chris Corless <chr...@atm.com> wrote in article <33122B...@atm.com>...
> Sorry, still no answer, I too am having problems setting this same thing
> up. I have an NT 3.51 server with SP4 installed. The server has an
> ethernet and token ring adapter installed with IP bound to both.
>
> I have set the machine up exactly as detailed in knowledgebase article
> Q123024 (how to configure windows NT as an IP router) but still no luck.
>
> The ethernet side is using IP address 193.119.18.19 with no default
> gateway specified and the token ring side uses address 149.82.163.100
> with a default gateway of 149.82.163.10. I have checked the IP routing
> setting within network setup.
>
Todd Webb
Marc,
As long as there isn't a router on the ethernet side and the clients are
pointed to the ethernet NIC in the NT box for their DG there should be no
DG for that NIC.
Todd Webb
tod...@flash.net
Ted Kaczmarek <t...@oasyscorp.com> wrote in article
<33163A...@oasyscorp.com>...