Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

Windows 2000 RRAS - Configuration problems

Posted on 2002-07-30
6
Medium Priority
?
297 Views
Last Modified: 2013-12-23
Hi, I've got a box running Windows 2000 AS, I'm trying to use RRAS to route between our two domains (192.168.54.1-255 and 192.168.56.1-255) and provide internet connectivity via the firewall (192.168.52.2).

The Windows Box has three network cards:
192.168.52.1
192.168.54.1
192.168.56.1

From any of the domains I can ping traffic throughout, eg 192.168.54.100 to 192.168.56.100, I can ping the firewalls internal address 192.168.52.2, from anywhere on the LAN, but the only place I can ping the External firewall address is from the Windows Box, on all the other machines tracert shows the route ending at the Windows box. eg 192.168.54.1 or 192.168.56.1.

This is obviously a routing problem with the Windows box, it is configured with NAT enabled. Below is the routing table.

Any help anyone can give me with this is much appreciated, using Linux is NOT an option and I would prefer not to use a thrid party application.

Many thanks

Chris Moon

===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 10 4b 45 86 78 ...... 3Com EtherLink PCI (Microsoft's Packet Scheduler)
0x3 ...00 01 02 a2 ee 65 ...... 3Com EtherLink PCI (Microsoft's Packet Scheduler)
0x1000005 ...00 b0 d0 38 5d 0e ...... 3Com EtherLink PCI (Microsoft's Packet Scheduler)
===========================================================================
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0     192.168.52.1    192.168.54.1       1
          0.0.0.0          0.0.0.0     192.168.52.1    192.168.52.1       1
        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1       1
     192.168.52.0    255.255.255.0     192.168.52.1    192.168.52.1       1
     192.168.52.1  255.255.255.255        127.0.0.1       127.0.0.1       1
   192.168.52.255  255.255.255.255     192.168.52.1    192.168.52.1       1
     192.168.54.0    255.255.255.0     192.168.54.1    192.168.54.1       1
     192.168.54.1  255.255.255.255        127.0.0.1       127.0.0.1       1
   192.168.54.255  255.255.255.255     192.168.54.1    192.168.54.1       1
        224.0.0.0        224.0.0.0     192.168.52.1    192.168.52.1       1
        224.0.0.0        224.0.0.0     192.168.54.1    192.168.54.1       1
  255.255.255.255  255.255.255.255     192.168.54.1    192.168.54.1       1
Default Gateway:      192.168.52.1
===========================================================================
Persistent Routes:
  None

0
Comment
Question by:cjcjcj
5 Comments
 
LVL 2

Expert Comment

by:edmonds_robert
ID: 7187996
I think the problem may be in the first line.  You show a default route with a gateway of 192.168.52.1, but it says to get there using the interface 192.168.54.1.  I don't think this will work very well.  Try deleting this line using the route delete command and see what happens.
0
 
LVL 9

Expert Comment

by:schmiegu
ID: 7208286
Obviously you have configured 2 NICs with a default gateway (192.168.54.1 and 192.168.52.1). And your default gateway 192.168.52.1 is wrong.
There can only be one default gateway, which you should set to NIC 192.168.52.1 as 192.168.52.2.

Depending on your firewall config you will not be able to ping the external firewall address (a properly configured firewall dismisses ICMP echo requests, at least at the external address), but connectivity should be ok.
0
 

Expert Comment

by:CleanupPing
ID: 9159957
cjcjcj:
This old question needs to be finalized -- accept an answer, split points, or get a refund.  For information on your options, please click here-> http:/help/closing.jsp#1 
EXPERTS:
Post your closing recommendations!  No comment means you don't care.
0
 

Author Comment

by:cjcjcj
ID: 10431619
I solved the problem, for some reason none of the routing worked when the box was initially started up, however once it was logged in, restarting both the RRAS services and Disabling/Enabling all the network cards starts the service flawlessly.

Thanks
CJ
0
 

Accepted Solution

by:
modulo earned 0 total points
ID: 11860923
PAQed, with points refunded (200)

modulo
Community Support Moderator
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Many of us in IT utilize a combination of roaming profiles and folder redirection to ensure user information carries over from one workstation to another; in my environment, it was to enable virtualization without needing a separate desktop for each…
Are you one of those front-line IT Service Desk staff fielding calls, replying to emails, all-the-while working to resolve end-user technological nightmares? I am! That's why I have put together this brief overview of tools and techniques I use in o…
Michael from AdRem Software explains how to view the most utilized and worst performing nodes in your network, by accessing the Top Charts view in NetCrunch network monitor (https://www.adremsoft.com/). Top Charts is a view in which you can set seve…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an anti-spam), the admin…

824 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question