Networking Forums

Networking Forums > Computer Networking > Windows Networking > NT 4.0 upgrade to 2003 - Routing failure

Reply
Thread Tools Display Modes

NT 4.0 upgrade to 2003 - Routing failure

 
 
Tom
Guest
Posts: n/a

 
      12-01-2003, 04:35 PM
Hi, I upgraded a 4.0 server that was routing another
network to the internet behind a firewall. So, routed
network routes through the server to get rerouted out to
the internet. Problem is that we cannot attach to the
routed network form the other side of the server; NT 4.0
had no problem doing this for us. Routed network gets to
the internet fine.

192.168.1.0 = Routed network
192.168.0.0 = Main Network
192.168.0.254 = default gate for Main
192.168.1.1 = Gateway for clients on Routed network

Users on 0.0 used to be able to see resources on 1.0 on
NT 4.0 but not on 2003 Routing. Does anybody know what
setting I'm missing on Routing & RAS? I have turned off
Basic firewall on the route.

Tom.

 
Reply With Quote
 
 
 
 
Bill Grant
Guest
Posts: n/a

 
      12-01-2003, 09:48 PM
How have you configured the RRAS router? It should be configured for LAN
routing only. If you enable NAT you will get to the Internet OK, but the
"public" side will not be able to access the "private" side. It should look
like this.

Firewall
192.168.0.254
|
workstations
192.168.0.x dg 192.168.0.254
|
192.168.0.1 dg 192.168.0.254
RRAS
192.168.1.1 dg blank
|
workstations
192.168.1.x dg 192.168.1.1

The firewall needs a static route to forward traffic for 192.168.1.0 to
the RRAS router. eg

192.168.1.0 255.255.255.0 192.168.0.1

"Tom" <(E-Mail Removed)> wrote in message
news:06f101c3b831$88180650$(E-Mail Removed)...
> Hi, I upgraded a 4.0 server that was routing another
> network to the internet behind a firewall. So, routed
> network routes through the server to get rerouted out to
> the internet. Problem is that we cannot attach to the
> routed network form the other side of the server; NT 4.0
> had no problem doing this for us. Routed network gets to
> the internet fine.
>
> 192.168.1.0 = Routed network
> 192.168.0.0 = Main Network
> 192.168.0.254 = default gate for Main
> 192.168.1.1 = Gateway for clients on Routed network
>
> Users on 0.0 used to be able to see resources on 1.0 on
> NT 4.0 but not on 2003 Routing. Does anybody know what
> setting I'm missing on Routing & RAS? I have turned off
> Basic firewall on the route.
>
> Tom.
>



 
Reply With Quote
 
Tom
Guest
Posts: n/a

 
      12-02-2003, 03:27 PM
Bill, you are correct Lan Routing only has been selected
under the General tab under routing and remote access.
The firewall has the static route entry in place as this
was all working on Nt 4.0. The problem solver was the
NAT for "public interface" under NAT/Basic firewall.
This was checked off originally as soon as I set it back
to private network it started routing back again.

Will the filters still be able to process under NAT now
that I've selected private network? We need to restrict
FTP for the 1.0 network.

Thanks!

Tom.





>-----Original Message-----
> How have you configured the RRAS router? It should be

configured for LAN
>routing only. If you enable NAT you will get to the

Internet OK, but the
>"public" side will not be able to access the "private"

side. It should look
>like this.
>
>Firewall
>192.168.0.254
> |
>workstations
>192.168.0.x dg 192.168.0.254
> |
>192.168.0.1 dg 192.168.0.254
> RRAS
>192.168.1.1 dg blank
> |
>workstations
>192.168.1.x dg 192.168.1.1
>
> The firewall needs a static route to forward traffic

for 192.168.1.0 to
>the RRAS router. eg
>
>192.168.1.0 255.255.255.0 192.168.0.1
>
>"Tom" <(E-Mail Removed)> wrote in message
>news:06f101c3b831$88180650$(E-Mail Removed)...
>> Hi, I upgraded a 4.0 server that was routing another
>> network to the internet behind a firewall. So, routed
>> network routes through the server to get rerouted out

to
>> the internet. Problem is that we cannot attach to the
>> routed network form the other side of the server; NT

4.0
>> had no problem doing this for us. Routed network gets

to
>> the internet fine.
>>
>> 192.168.1.0 = Routed network
>> 192.168.0.0 = Main Network
>> 192.168.0.254 = default gate for Main
>> 192.168.1.1 = Gateway for clients on Routed network
>>
>> Users on 0.0 used to be able to see resources on 1.0 on
>> NT 4.0 but not on 2003 Routing. Does anybody know what
>> setting I'm missing on Routing & RAS? I have turned off
>> Basic firewall on the route.
>>
>> Tom.
>>

>
>
>.
>

 
Reply With Quote
 
Bill Grant
Guest
Posts: n/a

 
      12-02-2003, 11:41 PM
As far as I know, the filters are independent of the NAT config. They
should still be active on the "external" interface of the server.

"Tom" <(E-Mail Removed)> wrote in message
news:004d01c3b8f1$2fc98170$(E-Mail Removed)...
> Bill, you are correct Lan Routing only has been selected
> under the General tab under routing and remote access.
> The firewall has the static route entry in place as this
> was all working on Nt 4.0. The problem solver was the
> NAT for "public interface" under NAT/Basic firewall.
> This was checked off originally as soon as I set it back
> to private network it started routing back again.
>
> Will the filters still be able to process under NAT now
> that I've selected private network? We need to restrict
> FTP for the 1.0 network.
>
> Thanks!
>
> Tom.
>
>
>
>
>
> >-----Original Message-----
> > How have you configured the RRAS router? It should be

> configured for LAN
> >routing only. If you enable NAT you will get to the

> Internet OK, but the
> >"public" side will not be able to access the "private"

> side. It should look
> >like this.
> >
> >Firewall
> >192.168.0.254
> > |
> >workstations
> >192.168.0.x dg 192.168.0.254
> > |
> >192.168.0.1 dg 192.168.0.254
> > RRAS
> >192.168.1.1 dg blank
> > |
> >workstations
> >192.168.1.x dg 192.168.1.1
> >
> > The firewall needs a static route to forward traffic

> for 192.168.1.0 to
> >the RRAS router. eg
> >
> >192.168.1.0 255.255.255.0 192.168.0.1
> >
> >"Tom" <(E-Mail Removed)> wrote in message
> >news:06f101c3b831$88180650$(E-Mail Removed)...
> >> Hi, I upgraded a 4.0 server that was routing another
> >> network to the internet behind a firewall. So, routed
> >> network routes through the server to get rerouted out

> to
> >> the internet. Problem is that we cannot attach to the
> >> routed network form the other side of the server; NT

> 4.0
> >> had no problem doing this for us. Routed network gets

> to
> >> the internet fine.
> >>
> >> 192.168.1.0 = Routed network
> >> 192.168.0.0 = Main Network
> >> 192.168.0.254 = default gate for Main
> >> 192.168.1.1 = Gateway for clients on Routed network
> >>
> >> Users on 0.0 used to be able to see resources on 1.0 on
> >> NT 4.0 but not on 2003 Routing. Does anybody know what
> >> setting I'm missing on Routing & RAS? I have turned off
> >> Basic firewall on the route.
> >>
> >> Tom.
> >>

> >
> >
> >.
> >



 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Ip Fowarding failure after upgrade to Windows 2003 Charlie M Windows Networking 2 12-06-2007 02:00 PM
Navi200 firmware upgrade failure Erik Palsbo Network Routers 0 01-28-2006 10:51 AM
MN-700 Firmware Upgrade Failure =?Utf-8?B?aXZhYmdu?= Broadband Hardware 3 11-30-2005 01:51 AM
VPN disconnect causes routing failure =?Utf-8?B?QW5keQ==?= Windows Networking 0 02-11-2005 08:31 PM
RAS routing failure Shu-Min Chang Windows Networking 0 12-19-2003 10:44 PM



1 2 3 4 5 6 7 8 9 10 11