RE: Routes being automatically added to WK3 server routing table
- From: v-jackyg@xxxxxxxxxxxxxxxxxxxx (Jacky Gu [MSFT])
- Date: Thu, 01 Sep 2005 10:13:41 GMT
Hello Crikan,
Sorry for the delay. I am now at office. I notice that you do not have
"Routing and Remote Access" enabled on this server. I wonder how the route
function is accomplished on this server?
If the unexpected routes are not added manually, as you mentioned, we can
enable Routing and Remote Access and follow the steps I provided in my last
reply to have a try. It should resolve your problem
Hope this helps.
Jacky Gu
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/
If you are outside the United States, please visit our International
Support page: http://support.microsoft.com/common/international.aspx
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| Subject: RE: Routes being automatically added to WK3 server routing table
| From: "crikan@xxxxxxxxxxxxxxxx" <crikan@xxxxxxxxxxxxxxxx>
| References: <OuepuuLqFHA.3516@xxxxxxxxxxxxxxxxxxxx>
<656yTZUqFHA.1204@xxxxxxxxxxxxxxxxxxxxx>
<#ose4lXqFHA.3680@xxxxxxxxxxxxxxxxxxxx>
<YqC5UUeqFHA.3800@xxxxxxxxxxxxxxxxxxxxx>
<umFjrdkqFHA.3424@xxxxxxxxxxxxxxxxxxxx>
| User-Agent: Xnews/5.04.25
| Message-ID: <OmAvmQmrFHA.2996@xxxxxxxxxxxxxxxxxxxx>
| Newsgroups: microsoft.public.windows.server.general
| Date: Wed, 31 Aug 2005 12:42:40 -0700
| NNTP-Posting-Host: host51-34.discord.birch.net 65.16.51.34
| Lines: 1
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.general:46455
| X-Tomcat-NG: microsoft.public.windows.server.general
|
| Jacky,
| Have you had a chance to look into my issue? thanks
| Crikan
|
| "crikan@xxxxxxxxxxxxxxxx" <crikan@xxxxxxxxxxxxxxxx> wrote in
| news:umFjrdkqFHA.3424@xxxxxxxxxxxxxxxxxxxx:
|
| > Jacky,
| >
| > I do not have "Routing and Remote Access" enabled/configured on this
| > server. This keeps me from being able to expand the server under
| > "Routing and Remote Access". Should I enable Routing and Remote
| Access
| > so I can disable RIP and OSPF? Are RIP and OSPF turned on by default?
| >
| >
| > -----------
| >| |
| >| Internet|
| >| |
| > -----------
| > |
| > |
| > |
| > -----------
| >| |
| >| Internet|
| >| Firewall|
| > -----------
| > |192.168.1.246
| > |
| > |
| > -----------
| >| |
| >|Corporate| 192.168.1.X
| >| LAN |
| > -----------
| > |
| > |
| > |192.168.1.16
| > -----------
| >|Corporate|
| >|Router |
| >| |-----------
| > ----------- |
| > |10.0.96.1 |10.1.9.1
| > | |
| > |10.0.96.2 |10.1.9.2
| > ----------- -----------
| >| Remote | | Remote |
| >| Office | | Office |
| >|Router096| |Router109|
| > ----------- -----------
| > |10.0.96.254 |10.1.9.254
| > | |
| > |10.0.96.150 |10.1.9.150
| > ----------- -----------
| >| Remote | | Remote |
| >|Computer | | Computer|
| >| 096 | | 109 |
| > ----------- -----------
| >
| >
| > Crikan
| >
| >
| >
| >
| > v-jackyg@xxxxxxxxxxxxxxxxxxxx (Jacky Gu [MSFT]) wrote in
| > news:YqC5UUeqFHA.3800@xxxxxxxxxxxxxxxxxxxxx:
| >
| >> Hello Crikan,
| >>
| >> Would you like to send us a topology image of your network
| >> environment? This image can help us to have clearer picture of this
| >> problem.
| >>
| >> You mentioned that the server has one persistent route installed and
| >> this route can communicate with those computers at the remote
| >> locations. If so, I think that we my remove the dynamic route
| protocol
| >> to avoid the 10.0.96.150 and 10.1.9.150 routes being added.
| >>
| >> To do this, please perform the following steps:
| >> 1. Click Start-->Administrative Tools-->Routing and Remote Access
| >> 2. Expand the server
| >> 3. Under IP Routing, right-click and delete the dynamic route
| protocol
| >> (Such as RIP and OSPF)
| >>
| >> Also, if you do not want to delete the dynamic route protocol, you
| >> could block the routes 10.0.96.150 and 10.1.9.150 by the following
| >> steps: 1. Click Start-->Administrative Tools-->Routing and Remote
| >> Access 2. Expand the server
| >> 3. Under IP Routing, right-click the dynamic route protocol (Such as
| >> RIP and OSPF) and click Properties
| >> 4. Under the Security tab, choose "Ignore announcements from all
| >> listed routers" and add the router addresses to the list.
| >>
| >> Hope this helps.
| >>
| >> Jacky Gu
| >>
| >> Microsoft Online Partner Support
| >>
| >> When responding to posts, please "Reply to Group" via your newsreader
| >> so that others may learn and benefit from your issue.
| >>
| >> =====================================================
| >>
| >> Business-Critical Phone Support (BCPS) provides you with technical
| >> phone support at no charge during critical LAN outages or "business
| >> down" situations. This benefit is available 24 hours a day, 7 days a
| >> week to all Microsoft technology partners in the United States and
| >> Canada.
| >>
| >> This and other support options are available here:
| >> BCPS:
| >>
| https://partner.microsoft.com/US/technicalsupport/supportoverview/4001
| > 0
| >> 469 Others:
| >> https://partner.microsoft.com/US/technicalsupport/supportoverview/
| >>
| >> If you are outside the United States, please visit our International
| >> Support page: http://support.microsoft.com/common/international.aspx
| >>
| >> =====================================================
| >>
| >> This posting is provided "AS IS" with no warranties, and confers no
| >> rights. --------------------
| >>| Subject: RE: Routes being automatically added to WK3 server routing
| >>| table From: "crikan@xxxxxxxxxxxxxxxx" <crikan@xxxxxxxxxxxxxxxx>
| >>| References: <OuepuuLqFHA.3516@xxxxxxxxxxxxxxxxxxxx>
| >> <656yTZUqFHA.1204@xxxxxxxxxxxxxxxxxxxxx>
| >>| User-Agent: Xnews/5.04.25
| >>| Message-ID: <#ose4lXqFHA.3680@xxxxxxxxxxxxxxxxxxxx>
| >>| Newsgroups: microsoft.public.windows.server.general
| >>| Date: Thu, 25 Aug 2005 06:32:41 -0700
| >>| NNTP-Posting-Host: host51-34.discord.birch.net 65.16.51.34
| >>| Lines: 1
| >>| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!
| TK2MSFTNGP15.phx.gbl
| >>| Xref: TK2MSFTNGXA01.phx.gbl
| >>| microsoft.public.windows.server.general:45910 X-Tomcat-NG:
| >>| microsoft.public.windows.server.general
| >>|
| >>| Jacky,
| >>| Actually it has three. The Exchange 5.5 NT 4.0 Server I
| had
| >>| before, only had 1 adapter in it, and it had the same problem. I
| >>| will remove the excess adapters the next time I do maintenance and
| >>| see if that cures the problem.
| >>| When the routes get added, the server can no longer
| >>| communicate
| >>| with the remote computers because the Gateway that is being used in
| >>| those routes are incorrect. When I do a "route delete" on those
| >>| routes they go away. Sometimes it will go months without the bogus
| >>| routes being added back, and sometimes it might happen 3 times in a
| >>| week. But mostly it seems to happen to two locations about every
| >>| three months. It's very random.
| >>|
| >>| Crikan
| >>|
| >>|
| >>| v-jackyg@xxxxxxxxxxxxxxxxxxxx (Jacky Gu [MSFT]) wrote in
| >>| news:656yTZUqFHA.1204@xxxxxxxxxxxxxxxxxxxxx:
| >>|
| >>| > Hello Crikan,
| >>| >
| >>| > I find that you may have two adapters on this server. Is it
| >>| > correct? If we remove the second one, what's the result?
| >>| >
| >>| > Also, if we use the command line "route delete IP" to delete the
| >>| > added routes, will these routes be added at once?
| >>| >
| >>| > In addition, I would like to know if the added routes cause any
| >>| > problem.
| >>| >
| >>| > Jacky Gu
| >>| >
| >>| > Microsoft Online Partner Support
| >>| >
| >>| > When responding to posts, please "Reply to Group" via your
| >>| > newsreader so that others may learn and benefit from your issue.
| >>| >
| >>| > =====================================================
| >>| >
| >>| > Business-Critical Phone Support (BCPS) provides you with technical
| >>| > phone support at no charge during critical LAN outages or
| "business
| >>| > down" situations. This benefit is available 24 hours a day, 7 days
| >>| > a week to all Microsoft technology partners in the United States
| >>| > and Canada.
| >>| >
| >>| > This and other support options are available here:
| >>| > BCPS:
| >>| >
| > https://partner.microsoft.com/US/technicalsupport/supportoverview/40
| >>| > 01
| >>| 0
| >>| > 469 Others:
| >>| > https://partner.microsoft.com/US/technicalsupport/supportoverview/
| >>| >
| >>| > If you are outside the United States, please visit our
| >>| > International Support page:
| >>| > http://support.microsoft.com/common/international.aspx
| >>| >
| >>| > =====================================================
| >>| >
| >>| > This posting is provided "AS IS" with no warranties, and confers
| no
| >>| > rights. --------------------
| >>| >| Subject: Routes being automatically added to WK3 server routing
| >>| >| table From: "crikan@xxxxxxxxxxxxxxxx" <crikan@xxxxxxxxxxxxxxxx>
| >>| >| User-Agent: Xnews/5.04.25
| >>| >| Message-ID: <OuepuuLqFHA.3516@xxxxxxxxxxxxxxxxxxxx>
| >>| >| Newsgroups: microsoft.public.windows.server.general
| >>| >| Date: Wed, 24 Aug 2005 07:54:07 -0700
| >>| >| NNTP-Posting-Host: host51-34.discord.birch.net 65.16.51.34
| >>| >| Lines: 1
| >>| >| Path:
| >>| >| TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP15.phx.gbl
| >>| >| Xref: TK2MSFTNGXA01.phx.gbl
| >>| >| microsoft.public.windows.server.general:45795 X-Tomcat-NG:
| >>| >| microsoft.public.windows.server.general
| >>| >|
| >>| >| I have an Exchange Server that occasionally gets incorrect routes
| >>| >| added to its routing table. I would like to prevent these routes
| >>| >| from being added.
| >>| >| The Exchange server is a Windows 2003 server, but this was also
| >>| >| happening to its predecessor, a Windows NT 4.0 Sever. The routes
| >>| >| are for computers that are on remote subnets that are connected
| to
| >>| >| our Corporate network via Private Frame Relay connections. I
| have
| >>| >| one persistent route installed on the Exchange Server so it can
| >>| >| communicate with those computers at the remote locations. Can
| you
| >>| >| tell me what could be adding the offending routes and what I can
| >>| >| do to stop it. Thanks in advanced.
| >>| >|
| >>| >| In this first Route Print it is the 10.0.96.150 and 10.1.9.150
| >>| >| routes that are causing the problems. The second route print is
| >>| >| what the routing table should look like.
| >>| >|
| >>| >|
| >>| >|
| >>| >| IPv4 Route Table
| >>| >|
| >>|
| > ======================================================================
| >>| >| == ===
| >>| >| Interface List
| >>| >| 0x1 ........................... MS TCP Loopback interface
| >>| >| 0x10003 ...00 04 76 f4 f2 a9 ...... 3Com 3C996B Gigabit Server
| NIC
| >>| >| 0x10004 ...00 30 6e 12 f9 62 ...... HP NetServer 10/100TX PCI LAN
| >>| >| Adapter
| >>| >| 0x10005 ...00 30 6e 12 f9 61 ...... HP NetServer 10/100TX PCI LAN
| >>| >| Adapter #2
| >>| >|
| >>|
| > ======================================================================
| >>| >| == ===
| >>| >|
| >>|
| > ======================================================================
| >>| >| == ===
| >>| >| Active Routes:
| >>| >| Network Destination Netmask Gateway Interface
| >>| >| Metric 0.0.0.0 0.0.0.0 192.168.1.246
| >>| >| 192.168.1.243 20 10.0.0.0 255.0.0.0
| 192.168.1.16
| >>| >| 192.168.1.243 1 10.0.96.150 255.255.255.255
| >>| >| 192.168.1.246 192.168.1.243 1 10.1.9.150 255.255.255.255
| >>| >| 192.168.1.246 192.168.1.243 1 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.243 192.168.1.243 20 192.168.1.243
| >>| >| 255.255.255.255 127.0.0.1 127.0.0.1 20
| >>| >| 192.168.1.255 255.255.255.255 192.168.1.243 192.168.1.243
| >>| >| 20 224.0.0.0 240.0.0.0 192.168.1.243 192.168.1.243
| >>| >| 20 255.255.255.255 255.255.255.255 192.168.1.243 10005
| >>| >| 1 255.255.255.255 255.255.255.255 192.168.1.243
| >>| >| 192.168.1.243 1 255.255.255.255 255.255.255.255
| >>| >| 192.168.1.243 10004 1 Default Gateway:
| >>| >| 192.168.1.246
| >>| >|
| >>|
| > ======================================================================
| >>| >| == ===
| >>| >| Persistent Routes:
| >>| >| Network Address Netmask Gateway Address Metric
| >>| >| 10.0.0.0 255.0.0.0 192.168.1.16 1
| >>| >|
| >>| >|
| >>| >|
| >>| >|
| >>| >| IPv4 Route Table
| >>| >|
| >>|
| > ======================================================================
| >>| >| == ===
| >>| >| Interface List
| >>| >| 0x1 ........................... MS TCP Loopback interface
| >>| >| 0x10003 ...00 04 76 f4 f2 a9 ...... 3Com 3C996B Gigabit Server
| NIC
| >>| >| 0x10004 ...00 30 6e 12 f9 62 ...... HP NetServer 10/100TX PCI LAN
| >>| >| Adapter
| >>| >| 0x10005 ...00 30 6e 12 f9 61 ...... HP NetServer 10/100TX PCI LAN
| >>| >| Adapter #2
| >>| >|
| >>|
| > ======================================================================
| >>| >| == ===
| >>| >|
| >>|
| > ======================================================================
| >>| >| == ===
| >>| >| Active Routes:
| >>| >| Network Destination Netmask Gateway Interface
| >>| >| Metric 0.0.0.0 0.0.0.0 192.168.1.246
| >>| >| 192.168.1.243 20 10.0.0.0 255.0.0.0
| >>| >| 192.168.1.16 192.168.1.243 1 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.243 192.168.1.243 20
| >>| >| 192.168.1.243 255.255.255.255 127.0.0.1 127.0.0.1
| >>| >| 20 192.168.1.255 255.255.255.255 192.168.1.243 192.168.1.243
| >>| >| 20 224.0.0.0 240.0.0.0 192.168.1.243
| >>| >| 192.168.1.243 20 255.255.255.255 255.255.255.255
| >>| >| 192.168.1.243 10005 1 255.255.255.255
| >>| >| 255.255.255.255 192.168.1.243 192.168.1.243 1
| >>| >| 255.255.255.255 255.255.255.255 192.168.1.243 10004
| >>| >| 1 Default Gateway: 192.168.1.246
| >>| >|
| >>|
| > ======================================================================
| >>| >| == ===
| >>| >| Persistent Routes:
| >>| >| Network Address Netmask Gateway Address Metric
| >>| >| 10.0.0.0 255.0.0.0 192.168.1.16 1
| >>| >|
| >>| >
| >>| >
| >>|
| >>|
| >>
| >
| >
|
|
.
- Follow-Ups:
- RE: Routes being automatically added to WK3 server routing table
- From: crikan@xxxxxxxxxxxxxxxx
- RE: Routes being automatically added to WK3 server routing table
- References:
- RE: Routes being automatically added to WK3 server routing table
- From: crikan@xxxxxxxxxxxxxxxx
- RE: Routes being automatically added to WK3 server routing table
- Prev by Date: Re: Windows 2003 connection freezes when using FTP server
- Next by Date: Re: Windows 2003 connection freezes when using FTP server
- Previous by thread: RE: Routes being automatically added to WK3 server routing table
- Next by thread: RE: Routes being automatically added to WK3 server routing table
- Index(es):
Relevant Pages
|
