Nt server routing problem

Nt server routing problem

Post by Sergio Novell » Fri, 14 Aug 1998 04:00:00



I have an internal network with C Class Ip address, and a router (Cisco
2500) as gateway to the Internet.
I want to set up an NT server (Alpha-based) with two NIC card, with
different IP address of my subnet.
One card is used to see the internal network, the other, connected to the
Cisco, to see the Internet.

The Cisco has IP xxx.xxx.xxx.1

The server has IP xxx.xxx.xxx.10    (internal, connected to an hub)
The server has IP xxx.xxx.xxx.11    (external, connected to the router)

I can see, from the server, the Internet and my internal network, but from
the network I can't see the Internet and viceversa.

I checked IP forwarding, but nothing happened.
I Installed the RRAS from MS, activated the RIP, but nothing
I set up my pc on the netowrk to use the xxx.xxx.xxx.10 as default gateway:
I can ping this card from the network, but not the external one (NIC B).

                                |                  |
|
                                |                  |
|
INTERNET    =====CISCO==|==NIC A ---NIC B===|    LAN
                                |                  |
|
                                |                  |
|

I seems that the the routing doesn't happens.
How can I use static route?

I need to set as gateway for NIC A the CISCO and NIC B?
I need to set as gateway for NIC N the NIC A?
What about default gateway for the server?
I need to modify my Router configuration?

I need help because I read a lot, and it seems I made everithing right but
it doesn't work.

Thanks in advance.

Sergio Novelli

Please, write also in my mailbox, because next two weeks i'll be away.

 
 
 

Nt server routing problem

Post by Lee Shar » Fri, 14 Aug 1998 04:00:00



|I have an internal network with C Class Ip address, and a router (Cisco
|2500) as gateway to the Internet.
|I want to set up an NT server (Alpha-based) with two NIC card, with
|different IP address of my subnet.
|One card is used to see the internal network, the other, connected to the
|Cisco, to see the Internet.

|The Cisco has IP xxx.xxx.xxx.1

|The server has IP xxx.xxx.xxx.10    (internal, connected to an hub)
|The server has IP xxx.xxx.xxx.11    (external, connected to the router)

   Got this far, and I know your problem.  You need to do some research on
subnetting. You have everything set up on the same subnet, and routing
doesn't work that way.  Bridging <layer 2 switching> does, but NT does not
bridge.  You need to subnet your network, set your subnet masks
appropriately, and then it will work fine.

            Lee

--
SCSI is *NOT* magic. There are *fundamental technical reasons* why it is
necessary to sacrifice a young goat to your SCSI chain now and then. *
Black holes are where God divided by zero. - I am speaking as an individual,
not as a representative of any company, organization or other entity.  I am
solely responsible for my words.

 
 
 

Nt server routing problem

Post by Matt Mille » Fri, 14 Aug 1998 04:00:00


Sergio:

This is a subnetting problem.  NT Server will NOT forward packets to addresses
which are supposed to be in the same block.  The block is determined by the
Subnet mask.  Take a look at the following table:

Subnet mask:            Block size (usable)                    Blocks in a
Class C address
255.255.255.0        256 addresses                           1 block
(0-255)
255.255.255.128    128 addresses each                    2 blocks   (0-127,
128-255)
255.255.255.192    64 each                                    4 blocks
(0-63,64-127,128-191,192-255)
etc.........

Note:    Each Block is delimited by two unusable addresses (first and last), so
a .192 mask actually defines 62 USABLE addresses.

Now that we've covered that, keep in mind what we stated earlier, which is that
NT does not forward packets within the same block.  IF both NIC's are part of
the same block, NT assumes that there is some direct cabling scheme somehow
connecting both NIC's and that the two sides will eventually get the message.
(you would want it to assume this if you DO in fact have two NIC's on the same
side for performance reasons, since it will cut down on your network chatter).

Trick here is to cut you assigned block into pieces, and put the NT server
between the two pieces.  For example:
                                IP address                        Subnet Mask
NIC1 (internal)        a.b.c.1                                255.255.255.128
NIC2 (external)        a.b.c.129                            255.255.255.128

if you refer to above, the two NIC's are not part of the same block, so routing
and packet forwarding will occur.

Problem here is to "keep" as many IP addresses on the Internal side as you can,
and keep the outside small.  Ideally, you could request a single IP address for
NIC2 from your ISP.  Just make the address something outside of your block, and
life is grand.   Otherwise, try this example:

NIC1            a.b.c.1                255.255.255.128
NIC2            a.b.c.252            255.255.255.248

You would then have to add some additional routes to your routing table, all of
them pointing to a.b.c.1.  In this example:
ROUTE ADD    A.B.C.128    255.255.255.192    A.B.C.1        ("recovers" 62
addresses)
ROUTE ADD    A.B.C.192    255.255.255.224    A.B.C.1        ("recovers" 30
addresses)
ROUTE ADD    A.B.C.224    255.255.255.240    A.B.C.1        ("recovers" 14
addresses)
ROUTE ADD    A.B.C.240    255.255.255.248    A.B.C.1        ("recovers" 6
addresses)

It's a royal pain to set up, but it does work and it is quite stable once you
do.

Hope this helps.


> I have an internal network with C Class Ip address, and a router (Cisco
> 2500) as gateway to the Internet.
> I want to set up an NT server (Alpha-based) with two NIC card, with
> different IP address of my subnet.
> One card is used to see the internal network, the other, connected to the
> Cisco, to see the Internet.

> The Cisco has IP xxx.xxx.xxx.1

> The server has IP xxx.xxx.xxx.10    (internal, connected to an hub)
> The server has IP xxx.xxx.xxx.11    (external, connected to the router)

> I can see, from the server, the Internet and my internal network, but from
> the network I can't see the Internet and viceversa.

> I checked IP forwarding, but nothing happened.
> I Installed the RRAS from MS, activated the RIP, but nothing
> I set up my pc on the netowrk to use the xxx.xxx.xxx.10 as default gateway:
> I can ping this card from the network, but not the external one (NIC B).

>                                 |                  |
> |
>                                 |                  |
> |
> INTERNET    =====CISCO==|==NIC A ---NIC B===|    LAN
>                                 |                  |
> |
>                                 |                  |
> |

> I seems that the the routing doesn't happens.
> How can I use static route?

> I need to set as gateway for NIC A the CISCO and NIC B?
> I need to set as gateway for NIC N the NIC A?
> What about default gateway for the server?
> I need to modify my Router configuration?

> I need help because I read a lot, and it seems I made everithing right but
> it doesn't work.

> Thanks in advance.

> Sergio Novelli

> Please, write also in my mailbox, because next two weeks i'll be away.

 
 
 

Nt server routing problem

Post by Henry Schlar » Sat, 15 Aug 1998 04:00:00


Thank you for this insight.
 
 
 

Nt server routing problem

Post by Matthias Fynes-Clinto » Sat, 15 Aug 1998 04:00:00


with the configuration shown, presumable the Cisco router has an external
NIC with a fully qualified IP address, so I prsume that the NIC's that
connect the router to the server could have whatver ip and subnet they want,
as they only need to talk to each other, thus eliminating the need to change
the internal network ip addressing
Regards
Matthias


>Sergio:

>This is a subnetting problem.  NT Server will NOT forward packets to
addresses
>which are supposed to be in the same block.  The block is determined by the
>Subnet mask.  Take a look at the following table:

>Subnet mask:            Block size (usable)                    Blocks in a
>Class C address
>255.255.255.0        256 addresses                           1 block
>(0-255)
>255.255.255.128    128 addresses each                    2 blocks   (0-127,
>128-255)
>255.255.255.192    64 each                                    4 blocks
>(0-63,64-127,128-191,192-255)
>etc.........

>Note:    Each Block is delimited by two unusable addresses (first and
last), so
>a .192 mask actually defines 62 USABLE addresses.

>Now that we've covered that, keep in mind what we stated earlier, which is
that
>NT does not forward packets within the same block.  IF both NIC's are part
of
>the same block, NT assumes that there is some direct cabling scheme somehow
>connecting both NIC's and that the two sides will eventually get the
message.
>(you would want it to assume this if you DO in fact have two NIC's on the
same
>side for performance reasons, since it will cut down on your network
chatter).

>Trick here is to cut you assigned block into pieces, and put the NT server
>between the two pieces.  For example:
>                                IP address                        Subnet
Mask
>NIC1 (internal)        a.b.c.1
255.255.255.128
>NIC2 (external)        a.b.c.129                            255.255.255.128

>if you refer to above, the two NIC's are not part of the same block, so
routing
>and packet forwarding will occur.

>Problem here is to "keep" as many IP addresses on the Internal side as you
can,
>and keep the outside small.  Ideally, you could request a single IP address
for
>NIC2 from your ISP.  Just make the address something outside of your block,
and
>life is grand.   Otherwise, try this example:

>NIC1            a.b.c.1                255.255.255.128
>NIC2            a.b.c.252            255.255.255.248

>You would then have to add some additional routes to your routing table,
all of
>them pointing to a.b.c.1.  In this example:
>ROUTE ADD    A.B.C.128    255.255.255.192    A.B.C.1        ("recovers" 62
>addresses)
>ROUTE ADD    A.B.C.192    255.255.255.224    A.B.C.1        ("recovers" 30
>addresses)
>ROUTE ADD    A.B.C.224    255.255.255.240    A.B.C.1        ("recovers" 14
>addresses)
>ROUTE ADD    A.B.C.240    255.255.255.248    A.B.C.1        ("recovers" 6
>addresses)

>It's a royal pain to set up, but it does work and it is quite stable once
you
>do.

>Hope this helps.


>> I have an internal network with C Class Ip address, and a router (Cisco
>> 2500) as gateway to the Internet.
>> I want to set up an NT server (Alpha-based) with two NIC card, with
>> different IP address of my subnet.
>> One card is used to see the internal network, the other, connected to the
>> Cisco, to see the Internet.

>> The Cisco has IP xxx.xxx.xxx.1

>> The server has IP xxx.xxx.xxx.10    (internal, connected to an hub)
>> The server has IP xxx.xxx.xxx.11    (external, connected to the router)

>> I can see, from the server, the Internet and my internal network, but
from
>> the network I can't see the Internet and viceversa.

>> I checked IP forwarding, but nothing happened.
>> I Installed the RRAS from MS, activated the RIP, but nothing
>> I set up my pc on the netowrk to use the xxx.xxx.xxx.10 as default
gateway:
>> I can ping this card from the network, but not the external one (NIC B).

>>                                 |                  |
>> |
>>                                 |                  |
>> |
>> INTERNET    =====CISCO==|==NIC A ---NIC B===|    LAN
>>                                 |                  |
>> |
>>                                 |                  |
>> |

>> I seems that the the routing doesn't happens.
>> How can I use static route?

>> I need to set as gateway for NIC A the CISCO and NIC B?
>> I need to set as gateway for NIC N the NIC A?
>> What about default gateway for the server?
>> I need to modify my Router configuration?

>> I need help because I read a lot, and it seems I made everithing right
but
>> it doesn't work.

>> Thanks in advance.

>> Sergio Novelli

>> Please, write also in my mailbox, because next two weeks i'll be away.

 
 
 

1. NT Workstation data server on NT Server Domain problems.

I am running a Windows network, with NT Server as the domain Controller with
Windows 9x and NT workstation clients. One of the data servers is running NT
Workstation and is not allowing more than 11 users to connect at one time.
Does anyone know of a way to get around this.

Secondly, is it possible to specify Workgroups in a domain an the NT
Workstation machines?

Any help will be greatly appreciated

2. 6530 emulation

3. Problem with Persistent routes on NT Server

4. disk probs

5. Problem - NT Server loses connection with ISP's DNS server

6. FOR THOSE WHO WANT TO TALK ABOUT COMMERCIAL GAME INFO

7. Problem - NT 4.0 Server disconnects from ISP's DNS Server

8. Voiceit manager

9. Connecting Linux Server to Windows NT Server using diald problem

10. NT Server To NT server VPN

11. NT Terminal Server routing thin clients

12. NT Server With IPX and static route

13. Routing with NT server?