Re: Urgent RRAS won't work Help!
From: Bill Grant (not.available_at_online)
Date: 05/11/04
- Next message: Bill Grant: "Re: Blocking non-Domain PCs from dialin"
- Previous message: Bill Grant: "Re: VPN hanging on verifiying username and password"
- Maybe in reply to: William Cooper: "Re: Urgent RRAS won't work Help!"
- Next in thread: William Cooper: "Re: Urgent RRAS won't work Help!"
- Reply: William Cooper: "Re: Urgent RRAS won't work Help!"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 11 May 2004 12:25:26 +1000
Where you need the extra routing is on the firewall. Because the default
route of the clients in the 192.168 subnet is to the firewall, that is where
your the traffic for 184.155 will go. The firewall will try to send it out
to the Internet, and any reply would go to the people who actully own those
IP addresses, not back to you!
Put a static route on the firewall to redirect traffic for 184.155.0 to
your Windows router. It will then be delivered, because that machine has an
interface in 184.155.0.0 . eg
184.155.0.0 255.255.0.0 192.168.200.7
"William Cooper" <nospamregcooper@hotmail.com> wrote in message
news:uf4KlWsNEHA.3052@TK2MSFTNGP12.phx.gbl...
Hi
Previously posted in microsoft.public.windows.server.networking, had some
responses but I have been unable to resolve the problem.
I have a problem with configuring a Win2k Server SP4 RRAS for routing. Okay
I have two networks 184.155.0.0 mask 255.255.0.0 and 192.168.200.0 mask
255.255.255.0. See attached jpg. There are two NICs in the RRAS server.
192.168.200.7 and 184.155.0.80. I have installed RRAS and built a router,
also disabled the
remote access bit as I don't need it. I have tried setting up the static
route but whatever config I use it won't route. The clients on the
184.155.0.0 network have the default gateway set as 184.155.0.80 via DHCP.
They can ping both NICs in the 2k server, but nothing else on the
192.168.200.0 network. The 2k RRAS server can ping clients on both networks.
I don't want to route DHCP requests as there is a DHCP server on each
network. What am I missing help! I set this up once before about a year ago
and it worked, don't think I used static routes though. Lost config in
urgent OS change.
If I do a route add 184.155.0.0 mask 255.255.0.0 192.168.200.7 on my DC, NOT
THE ROUTER, 184.155.0.0 clients can ping servers in the 192.168.200.0
network, but not the firewall 192.168.200.1. (SmoothWall) Previously I had
this working, and I even created a subnet on the firewall to grant various
port access rights to clients on the 184.155.0.0 network. The source IP on
the firewall rule was 192.168.200.7. Thus access control was based on
requests coming from this IP address, the router. This all worked a treat
before, I could control port access on the internet etc..
This is causing major problems for clients on the 184.155.0.0 network; Any
help will be very welcome.
William
PS I know that 184.155.0.0 is an class B address, but it is a closed network
and I have no control over the addressing scheme.
- Next message: Bill Grant: "Re: Blocking non-Domain PCs from dialin"
- Previous message: Bill Grant: "Re: VPN hanging on verifiying username and password"
- Maybe in reply to: William Cooper: "Re: Urgent RRAS won't work Help!"
- Next in thread: William Cooper: "Re: Urgent RRAS won't work Help!"
- Reply: William Cooper: "Re: Urgent RRAS won't work Help!"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
