Re: route delete not working

From: Phillip Windell (_at_.)
Date: 05/27/04 

Date: Thu, 27 May 2004 09:11:49 -0500

Never heard of a Network Dispatcher. That doesn't mean anything to me.

I believe Loop Back is the problem. It should not be in the same subnet as
the primary NIC. Give it the same mask of 255.255.252.0 and set the third
octect either above 135 or below 132. It is the same principle of not
having two NICs in the same physical machine that on on the same logical
subnet.

If you have a machine with multiple IP#s in the same subnet then they either
need to be bound on the same physical NIC or if using multiple NICS then
they should be "bridged" to gether. Otherwise if you want two NICs in a
machine, then they need to be different subnets and only one may have a
Default Gateway.

That's my take on it, but I admit I don't fully understand your situation. 

-- 
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
"TomP" <tp01tp012000@yahoo.com> wrote in message
news:132a701c443d1$3870f810$a301280a@phx.gbl...
> Hi Phil,
>
>   The route -f did delete the 9.0.0.0 route along with
> other routes I need.  This machine is front-ended by a
> Network Dispatcher.  This is the reason for the loopback
> adapter.
>
> Here's the output of ifconfig /all
> Windows IP Configuration
>
>    Host Name . . . . . . . . . . . . : pir01pc19
>
>    Primary Dns Suffix  . . . . . . . :
> pie.notesdev.ibm.com
>
>    Node Type . . . . . . . . . . . . : Hybrid
>
>    IP Routing Enabled. . . . . . . . : No
>
>    WINS Proxy Enabled. . . . . . . . : No
>
>    DNS Suffix Search List. . . . . . :
> pie.notesdev.ibm.com
>
>                                        notesdev.ibm.com
>
>                                        lotus.com
>
>                                        ibm.com
>
>
>
> Ethernet adapter Local Area Connection:
>
>
>
>    Connection-specific DNS Suffix  . :
> pie.notesdev.ibm.com
>
>    Description . . . . . . . . . . . : IBM Netfinity
> 10/100 Ethernet Adapter
>
>    Physical Address. . . . . . . . . : 00-09-6B-9A-13-F4
>
>    DHCP Enabled. . . . . . . . . . . : Yes
>
>    Autoconfiguration Enabled . . . . : Yes
>
>    IP Address. . . . . . . . . . . . : 9.33.135.23
>
>    Subnet Mask . . . . . . . . . . . : 255.255.252.0
>
>    Default Gateway . . . . . . . . . : 9.33.132.1
>
>    DHCP Server . . . . . . . . . . . : 9.33.151.11
>
>    DNS Servers . . . . . . . . . . . : 9.33.151.11
>
>                                        9.33.151.12
>
>    Primary WINS Server . . . . . . . : 9.33.151.11
>
>    Secondary WINS Server . . . . . . : 9.33.151.12
>
>    Lease Obtained. . . . . . . . . . : Wednesday, May 26,
> 2004 8:54:36 AM
>
>    Lease Expires . . . . . . . . . . : Monday, May 31,
> 2004 8:54:36 AM
>
>
>
> Ethernet adapter Local Area Connection 3:
>
>
>
>    Connection-specific DNS Suffix  . :
>
>    Description . . . . . . . . . . . : Microsoft Loopback
> Adapter
>
>    Physical Address. . . . . . . . . : 02-00-4C-4F-4F-50
>
>    DHCP Enabled. . . . . . . . . . . : No
>
>    IP Address. . . . . . . . . . . . : 9.33.132.64
>
>    Subnet Mask . . . . . . . . . . . : 255.0.0.0
>
>    Default Gateway . . . . . . . . . :
>
>
>
>
> >-----Original Message-----
> >If you don't mind doing it, after you've done the
> previous instructions, and
> >if there is still problems,...run "IPCONFIG /ALL" from a
> command prompt
> >window and post the results. The Route Table will
> rebuild based on the
> >network settings of all the interfaces, so if there is a
> problem, then it
> >would be a problem with the inteface configuration of
> one the interfaces.
> >
> >
> >-- 
> >
> >Phillip Windell [MCP, MVP, CCNA]
> >www.wandtv.com
> >
> >
> >"Phillip Windell" <@.> wrote in message
> >news:euc%23CR1QEHA.3944@tk2msftngp13.phx.gbl...
> >> C:\> Route -f
> >>
> >> Then reboot to rebuild the table.
> >>
> >>
> >> -- 
> >>
> >> Phillip Windell [MCP, MVP, CCNA]
> >> www.wandtv.com
> >>
> >>
> >> "Tom P" <tp01tp01@yahoo.com> wrote in message
> >> news:1311601c44351$0363f170$a101280a@phx.gbl...
> >> > Hi,
> >> >   I'm trying to delete a 9.0.0.0 route created when I
> >> > defined a loopback adapter.  I've tried many
> variations
> >> > of the route delete cmd w/out any luck.
> >> >
> >> > This machine was migrated from 2002 to 2003.  The
> >> > loopback adapter and route delete were running fine
> on
> >> > 2002.
> >> >
> >> >    C:\>route delete 9.0.0.0
> >> > The route specified was not found.
> >> >
> >> >
> >> > C:\>netstat -rn
> >> >
> >> > IPv4 Route Table
> >> >
> ==========================================================
> >> > =================
> >> > Interface List
> >> > 0x1 ........................... MS TCP Loopback
> interface
> >> > 0x2 ...02 00 4c 4f 4f 50 ...... Microsoft Loopback
> Adapter
> >> > 0x10004 ...00 09 6b 9a 13 f4 ...... IBM Netfinity
> 10/100
> >> > Ethernet Adapter
> >> >
> ==========================================================
> >> > =================
> >> >
> ==========================================================
> >> > =================
> >> > Active Routes:
> >> > Network Destination        Netmask          Gateway
> >> > Interface  Metric
> >> >           0.0.0.0          0.0.0.0       9.33.132.1
> >> > 9.33.135.23      1
> >> >           9.0.0.0        255.0.0.0      9.33.132.64
> >> > 9.33.132.64      1
> >> >        9.33.132.0    255.255.252.0      9.33.135.23
> >> > 9.33.135.23      1
> >> >       9.33.132.64  255.255.255.255
> >> > 127.0.0.1        127.0.0.1      1
> >> >       9.33.135.23  255.255.255.255
> >> > 127.0.0.1        127.0.0.1      1
> >> >     9.255.255.255  255.255.255.255      9.33.132.64
> >> > 9.33.132.64      1
> >> >     9.255.255.255  255.255.255.255      9.33.135.23
> >> > 9.33.135.23      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      9.33.132.64
> >> > 9.33.132.64      1
> >> >         224.0.0.0        240.0.0.0      9.33.135.23
> >> > 9.33.135.23      1
> >> >   255.255.255.255  255.255.255.255      9.33.132.64
> >> > 9.33.132.64      1
> >> >   255.255.255.255  255.255.255.255      9.33.135.23
> >> > 9.33.135.23      1
> >> > Default Gateway:        9.33.132.1
> >> >
> ==========================================================
> >> > =================
> >> > Persistent Routes:
> >> >   None
> >> >
> >> > C:\>
> >>
> >>
> >
> >
> >.
> >

Relevant Pages

  • Re: Multiple NICS on same subnet
    ... multiple NICs on the same subnet. ... No packets are *ever* route to this interface. ...
    (comp.os.linux.networking)
  • Re: FC1 multiple ethernet interface issue
    ... >> Here is the dump from ip route list for various modes of the nics. ... > Note that the default route has switched to the eth1 interface. ... of the subnet associated with the router and the interface. ...
    (Fedora)
  • Re: Routing quesiton (maybe specific to Nokia IP130 router?)
    ... If you are asking how to route to a directly connected subnet, ... have to do anything other than configure the router interface. ... To configure the interface; Voyager> IP address, subnet, speed, duplex, ...
    (comp.security.firewalls)
  • Re: TCP/IP Cluster Alias question
    ... > would like users to be able to connect to the cluster alias DSPSRV1, ... > and on the other subnet I would like then to connect to DSPSRV2. ... route for TCPIP. ... over the other interface. ...
    (comp.os.vms)
  • Re: XP Professional Routing
    ... Routing may well be configured correctly on the XP machine. ... order for traffic to be routed correctly from some computer on the subnet ... points to the IP address of adapter A. AND the gateway attached to adapter ... B must have a static route which sends traffic destined for the remote ...
    (microsoft.public.windowsxp.network_web)