Re: RRAS Routing Problems

Robert,

I'm glad we're coming to the same conclusions on the routing tables and
setup, at least I know I'm not crazy.

As for the traffic, pings succeed from the Fairfax RRAS box to the Boston
RASS box, and strangely enough even pinging CLIENTS on the Boston side from
the Fairfax RRAS box succeeds. When pinging the Fairfax RRAS box from Boston,
however, failure occurs. The tracert from the Boston RRAS box to the Fairfax
RRAS box fails right from the start, so at least it doesn't appear to be
erroneously routing through the DSL router.

Let me know what you think,

Jack

"Robert L. (MS-MVP)" wrote:

The routing tables look good to me. Where the traffic stop if using tracert
from Fairfax to Boston? Do you have NAT/Firewall enabled?

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"Jack Dawsen" <JackDawsen@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:149D34AB-B32F-4E69-A72B-BD8AFEF3C30D@xxxxxxxxxxxxxxxx
Robert,

That completely slipped my mind, I had every intention of posting the
routing tables.

This is the table from Boston:

Network Destination Netmask Gateway Interface
Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.29 20
72.85.61.11 255.255.255.255 192.168.1.1 192.168.1.29 20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.1.0 255.255.255.0 192.168.1.29 192.168.1.29 20
192.168.1.10 255.255.255.255 192.168.2.201 192.168.2.201 1
192.168.1.11 255.255.255.255 127.0.0.1 127.0.0.1 50
192.168.1.29 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.1.255 255.255.255.255 192.168.1.29 192.168.1.29 20
192.168.2.0 255.255.255.0 192.168.1.10 192.168.2.201 1
192.168.2.201 255.255.255.255 127.0.0.1 127.0.0.1 50
192.168.2.255 255.255.255.255 192.168.2.201 192.168.2.201 50
224.0.0.0 240.0.0.0 192.168.1.29 192.168.1.29 20
224.0.0.0 240.0.0.0 192.168.2.201 192.168.2.201 50
255.255.255.255 255.255.255.255 192.168.1.29 192.168.1.29 1
255.255.255.255 255.255.255.255 192.168.2.201 192.168.2.201 1
Default Gateway: 192.168.1.1
--

And this is the table from Fairfax:

Network Destination Netmask Gateway Interface
Metric
0.0.0.0 0.0.0.0 192.168.2.1 192.168.2.29 286
67.101.123.140 255.255.255.255 192.168.2.1 192.168.2.29 31
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
192.168.1.0 255.255.255.0 192.168.2.201 192.168.1.10 31
192.168.1.10 255.255.255.255 On-link 192.168.1.10 286
192.168.2.0 255.255.255.0 On-link 192.168.2.29 286
192.168.2.29 255.255.255.255 On-link 192.168.2.29 286
192.168.2.200 255.255.255.255 On-link 192.168.2.200 306
192.168.2.255 255.255.255.255 On-link 192.168.2.29 286
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 192.168.2.29 286
224.0.0.0 240.0.0.0 On-link 192.168.2.200 306
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 192.168.2.29 286
255.255.255.255 255.255.255.255 On-link 192.168.2.200 306
255.255.255.255 255.255.255.255 On-link 192.168.1.10 286
--

Thank you in advance for any guidance you can provide!

Jack

"Robert L. (MS-MVP)" wrote:

Posting the routing tables on both servers may help.

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"Jack Dawsen" <Jack Dawsen@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5A2B34B5-FF37-4717-9BEA-831E067EB725@xxxxxxxxxxxxxxxx
I have one of the weirdest routing problems I've ever seen in RRAS. I
have
the following configuration, :

Boston:
-All clients default routed to the RRAS Server
-Network: 192.168.1.0
-RRAS Server: 192.168.1.29
--Windows 2003 SP 2 (Enterprise Server)
--PPTP Server
--Static route set to the remote route on the 192.168.2.0 network
--One NIC, default routed to 192.168.1.1 (DSL Router to the cloud)

Fairfax:
-All clients default routed to the RRAS Server
-Network: 192.168.2.0
-RRAS Server: 192.168.2.29
--Windows 2008 (Enterprise Server)
--PPTP Server
--Static route set to the remote route on the 192.168.1.0 network
--One NIC, default routed to 192.168.2.1 (DSL Router to the cloud)

These servers have a route called BostonFairfaxRoute. It's set up
identically on both servers, using that username and the username's
password.
The RRAS servers connect the remote route successfully.

The problem lies in the ability to successfully route packets. The
following
scenarios result:

192.168.2.29: CAN PING 192.168.1.29
192.168.1.29: Cannot ping 192.168.2.29
Clients on 192.168.2.0 network: Cannot ping 192.168.1.29
Clients on the 192.1.0 network: Cannot ping 192.168.2.29

If the path between 192.168.2.29 and 192.168.1.29 didn't make it either
way
I'd understand the problem. The confusing part is that it works one
way!
I've
never seen this before and have no idea how to solve it. I've verified
all
of
the settings more than once in what's a very common system for me to
setup.

Anyone have any ideas?




.

Relevant Pages

  • Re: RDP can not logon error
    ... Tracert & Ping to dc on the same subnet as the server that is having trouble. ... No network provider accepted the given network path.. ... Starting test: CrossRefValidation ...
    (microsoft.public.windows.server.general)
  • Re: RDP can not logon error
    ... ping and tracert to the dc in that remote site (where this system ... Tracert & Ping to dc on the same subnet as the server that is having ... No network provider accepted the given network path.. ... Starting test: CrossRefValidation ...
    (microsoft.public.windows.server.general)
  • Re: DNS but No Web
    ... Routng how toTo setup Windows 2000/2003 as a router for a LAN, you need to two network adapters. ... To enable LAN routing. ... the server IP routing is disable that is the problem. ...
    (microsoft.public.windows.server.networking)
  • RE: VPN Resolution
    ... Microsoft CSS Online Newsgroup Support ... I currently am running a windows SBS2003 network and ... | cards, the member server has 1 nic, all nic's have static IP's. ... I can ping any address on the ...
    (microsoft.public.windows.server.sbs)
  • Re: Win2003 - Simple Quest, big Problem - Cant ping anywhere
    ... Post back with the routing table here may help. ... This server is behind the ... are addresses from the same network all of the servers are on. ... the ras server. ...
    (microsoft.public.win2000.ras_routing)