RE: Route added by RRAS that overrides local LAN route on NIC

Yes I have done all of these steps. I have intalled about 10 SBS systems and
performed the same set-up on all of them. This one for some reason has this
additional route problem. Can you tell me what causes this additional route
to be added? Is there a way to control the routes that RRAS adds to the
server when the client connects? Since it is adding a route to the full
subnet when the client connects it is behaving to me like a demain dial
connection that you would set-up between two servers, but I have it set-up to
an Access Server.

Any chance it has someting to do with 10.0.0.0/24 addressing on the box?
the 10.x.x.x private block is a Class A block which I am subnetting to be a
Class C. Could this be confusing RRAS?

John

""Crina Li"" wrote:

Hi John,

Thanks for your update.

From current situation, please check if you have configured the network
correctly on SBS and client computer:

SBS:

IP: Fixed IP address
Gateway: your Hardware router IP
DNS: SBS NIC IP as the only entry

In the DNS console (dnsmgmt.msc), right click your ServerName and click
properties. In the Forwarders tab, your ISP DNS server IP should be
inputted there.

On the client workstation, please make sure the configuration:

IP: Assigned by DHCP on SBS or your hardware router
Gateway: hardware router
DNS: SBS INTERNAL NIC IP as the only entry

And then recreate VPN to see if it helps. Please make sure you have
disabled the second NIC on the SBS.

Thanks for your time and I look forward to hearing from you.

Best regards,

Crina Li (MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.

=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| Thread-Topic: Route added by RRAS that overrides local LAN route on NIC
| thread-index: AcbsHRHUAAf6uugcSyW0/DF1OTvIWA==
| X-WBNR-Posting-Host: 65.184.34.228
| From: =?Utf-8?B?Sm9obiBQaGlsaXBz?= <JohnPhilips@xxxxxxxxxxxxxxxxxxxxxxxxx>
| References: <850ACC3C-EA74-409F-9BE7-D86A2147AFF0@xxxxxxxxxxxxx>
<wrMbnC36GHA.4348@xxxxxxxxxxxxxxxxxxxxx>
| Subject: RE: Route added by RRAS that overrides local LAN route on NIC
| Date: Mon, 9 Oct 2006 20:35:02 -0700
| Lines: 312
| Message-ID: <D350384D-3067-45AC-A911-C90363B45A1E@xxxxxxxxxxxxx>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
| Newsgroups: microsoft.public.windows.server.sbs
| Path: TK2MSFTNGXA01.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:303842
| NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| I am using SBS as the VPN server. This is a router between SBS and the
| internet that is peforming NAT. I have the appropriate ports open and can
| successfully connect a WinXP RAS client to the VPN server. The problem
is
| with the routes that get created on the RRAS when the client connects,
not
| getting a successful connection. When the connection is up I can
successful
| get to the SBS server across the VPN. My issue is with the disruption to
the
| connectivity to the other PCs on the LAN.
|
| Let me clarify what's happening with hopes you have seen this before:
|
| The server has a LAN address of 10.0.0.1 and is on a network 10.0.0.0/24.
| The route I am speaking of is the route to local LAN that is put in the
| routing table when you configure the NIC. In my case this route looks
like
| this:
|
| Network Dest Netmask Gateway Interface Metric
| 10.0.0.0 255.255.255.0 10.0.0.1 10.0.0.1 10
|
| 10.0.0.1 is the LAN address.
|
| After the RAS client connects there is another route added so the two
| entries of interest look like this:
|
| Network Dest Netmask Gateway Interface Metric
| 10.0.0.0 255.255.255.0 10.0.0.1 10.0.0.1 10 <-this route is always there
| (before and after the VPN cient connects)
| 10.0.0.0 255.255.255.0 10.0.0.115 10.0.0.121 1 <-this
| route added when client connects (in addtion to the host route that is
also
| added like you usually see for each client)
|
| 10.0.0.115 is the address assigned to the RAS client (using DHCP).
| 10.0.0.121 is the Internal Interface on the server used by RAS. As you
can
| see after this route is added the server is routing to 10.0.0.0 via the
RAS
| tunnel vs. the LAN Interface so the PCs on the 10.0.0.0/24 local subnet
are
| "disconnected" from the server. The only thing I could think of what that
| this was related to something that is configured automatically since
there
| are two NICs in the server, but I ran the the Internet Connection wizard
and
| set-up up the server to use one NIC for Internet and LAN.
|
| I was able to pull the ipconfig and routing table (without and with RAS
cient
| connected) from the server. They are below.
|
| As you will see by the route table, there is a route as I described .
| Network Destination Netmask Gateway Interface
Metric
| 0.0.0.0 0.0.0.0 10.0.0.254 10.0.0.1
1
| <------- Default route
| 10.0.0.0 255.255.255.0 10.0.0.1 10.0.0.1
10
| <----------- Route for interface LAN
|
| After the RAS client connects, I get a 2nd entry for
10.0.0.0/255.255.255.0
| but the gateway is the RAS client's assigned address, the Interface is
the
| RRAS internal interface address, and the metic is 1. This causes the
server
| to route all traffic destined for the local LAN to be routed over the
tunnel
| to the remote client. As expected the resulting effect is the server
cannot
| route packets to any of the machines on the local LAN which is very bad as
| as it breaks the local area network.
|
| Output of ipconfig /all and route print (without RAS client connected).
|
| Windows IP Configuration
|
| Host Name . . . . . . . . . . . . : SERVER1
| Primary Dns Suffix . . . . . . . : kuzma.local
| Node Type . . . . . . . . . . . . : Unknown
| IP Routing Enabled. . . . . . . . : Yes
| WINS Proxy Enabled. . . . . . . . : Yes
| DNS Suffix Search List. . . . . . : kuzma.local
|
| PPP adapter RAS Server (Dial In) Interface:
|
| Connection-specific DNS Suffix . :
| Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
| Physical Address. . . . . . . . . : 00-53-45-00-00-00
| DHCP Enabled. . . . . . . . . . . : No
| IP Address. . . . . . . . . . . . : 10.0.0.121
| Subnet Mask . . . . . . . . . . . : 255.255.255.255
| Default Gateway . . . . . . . . . :
| NetBIOS over Tcpip. . . . . . . . : Disabled
|
| Ethernet adapter Server Local Area Connection:
|
| Connection-specific DNS Suffix . :
| Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
Connection
| Physical Address. . . . . . . . . : 00-13-72-F7-3C-AB
| DHCP Enabled. . . . . . . . . . . : No
| IP Address. . . . . . . . . . . . : 10.0.0.1
| Subnet Mask . . . . . . . . . . . : 255.255.255.0
| Default Gateway . . . . . . . . . : 10.0.0.254
| DNS Servers . . . . . . . . . . . : 10.0.0.1
|
|
| C:\Documents and Settings\Administrator>route print (without RAS client
| connected)
|
| IPv4 Route Table
|
===========================================================================
| Interface List
| 0x1 ........................... MS TCP Loopback interface
| 0x10002 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
| 0x10003 ...00 13 72 f7 3c ab ...... Intel(R) PRO/1000 MT Network
Connection
|
===========================================================================
|
===========================================================================
| Active Routes:
| Network Destination Netmask Gateway Interface
Metric
| 0.0.0.0 0.0.0.0 10.0.0.254 10.0.0.1
1
| 10.0.0.0 255.255.255.0 10.0.0.1 10.0.0.1
10
| 10.0.0.1 255.255.255.255 127.0.0.1 127.0.0.1
10
| 10.0.0.121 255.255.255.255 127.0.0.1 127.0.0.1
50
| 10.255.255.255 255.255.255.255 10.0.0.1 10.0.0.1
10
| 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
1
| 224.0.0.0 240.0.0.0 10.0.0.1 10.0.0.1
10
| 255.255.255.255 255.255.255.255 10.0.0.1 10.0.0.1
1
| Default Gateway: 10.0.0.254
|
===========================================================================
| Persistent Routes:
| None
|
| Microsoft Windows [Version 5.2.3790]
| (C) Copyright 1985-2003 Microsoft Corp.
|
| C:\Documents and Settings\Administrator>route print (after RAS client
| connects)
|
| IPv4 Route Table
|
===========================================================================
| Interface List
| 0x1 ........................... MS TCP Loopback interface
| 0x10002 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
| 0x10003 ...00 13 72 f7 3c ab ...... Intel(R) PRO/1000 MT Network
Connection
|
===========================================================================
|
===========================================================================
| Active Routes:
| Network Destination Netmask Gateway Interface
Metric
| 0.0.0.0 0.0.0.0 10.0.0.254 10.0.0.1
1
| 10.0.0.0 255.255.255.0 10.0.0.1 10.0.0.1
10
| 10.0.0.0 255.255.255.0 10.0.0.115 10.0.0.121
1
| <- note this route is added when the RAS client connects which overrides
the
| route above to the local LAN
| 10.0.0.1 255.255.255.255 127.0.0.1 127.0.0.1
10
| 10.0.0.115 255.255.255.255 10.0.0.121 10.0.0.121
1
| 10.0.0.121 255.255.255.255 127.0.0.1 127.0.0.1
50
| 10.255.255.255 255.255.255.255 10.0.0.1 10.0.0.1
10
| 65.184.34.228 255.255.255.255 10.0.0.254 10.0.0.1
1
| 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
1
| 224.0.0.0 240.0.0.0 10.0.0.1 10.0.0.1
10
| 255.255.255.255 255.255.255.255 10.0.0.1 10.0.0.1
1
| Default Gateway: 10.0.0.254
|
===========================================================================
| Persistent Routes:
| None
|
| Have you ever heard of this before. What would be making RRAS add this
route?
|
| Thanks,
| John
|
| ""Crina Li"" wrote:
|
.

Relevant Pages

  • RE: Fax monitor incoming + outgoing calls?
    ... problem between the client computer and the SBS server. ... Client is using the internal IP address of the SBS server as the ... To the folder redirection GPO issue: ...
    (microsoft.public.windows.server.sbs)
  • RE: (Very) Slow browsing server shares - Net Work Monitor shows ca
    ... If this issue happen only when browse shared folders on SBS from one XP ... client computer, this will be a client side error. ... click to check the "Hide All Microsoft Services" ... Digitally sign communications (if server ...
    (microsoft.public.windows.server.sbs)
  • RE: No Client or Server Desktop Access Through RWW SBS 2003 SP2
    ... internal client Remote Desktop via RWW. ... Please perform the steps on the SBS and internal client computers: ... Click Remote tab, tick Enable Remote Desktop on this computer ... On the SBS server, click Start, click Run, type "regedit" (without the ...
    (microsoft.public.windows.server.sbs)
  • RE: trouble with shared fax service
    ... Thank you for posting in SBS newsgroup. ... install fax service on client computers. ... the SBS server or on the client workstation. ... and then choose 'Install' for the 'Fax Services' item. ...
    (microsoft.public.windows.server.sbs)
  • Re: Small Biz Design
    ... After we installed SBS 2003 successfully on the server box, the Client ... >When we setup SBS 2003 server using installation disks, ...
    (microsoft.public.windows.server.sbs)