Dynamips-Issues with connecting to hosts via TermServ

 Please help... Two issues

 A) For some reason I cant connect to any hosts from the "TermServ". I am using secureCRT to connect to TermServ however I can telnet directly to Hosts!!

OS: Windows 7

TermServ>R1

Trying R1 (169.254.0.1, 2001)...
TermServ>sh hosts
Default domain is not set
Name/address lookup uses static mappings

Codes: UN - unknown, EX - expired, OK - OK, ?? - revalidate
       temp - temporary, perm - permanent
       NA - Not Applicable None - Not defined

Host                      Port  Flags      Age Type   Address(es)
disalbe                   None  (temp, UN)  0
R1                        2001  (perm, OK)  0   IP    169.254.0.1
R2                        2002  (perm, OK)  0   IP    169.254.0.1
R3                        2003  (perm, OK)  0   IP    169.254.0.1
R4                        2004  (perm, OK)  0   IP    169.254.0.1
R5                        2005  (perm, OK)  0   IP    169.254.0.1
R6                        2006  (perm, OK)  0   IP    169.254.0.1
SW1                       2007  (perm, OK)  0   IP    169.254.0.1
SW2                       2008  (perm, OK)  0   IP    169.254.0.1
SW3                       2009  (perm, OK)  0   IP    169.254.0.1
SW4                       2010  (perm, OK)  0   IP    169.254.0.1
BB1                       2011  (perm, OK)  0   IP    169.254.0.1
BB2                       2012  (perm, OK)  0   IP    169.254.0.1
BB3                       2013  (perm, OK)  0   IP    169.254.0.1
disalbe                   NA    (temp, UN)  0  X.121

 

B) *Mar  1 00:50:20.467: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on Ethernet0/0 (not full duplex), with "masked hostname.doamin" FastEthernet4/35 (full duplex).

TermServ#sh ip int br
Interface                  IP-Address      OK? Method Status                Protocol
Ethernet0/0                169.254.0.2     YES NVRAM  up                    up     
Ethernet0/1                unassigned      YES unset  administratively down down   
Ethernet0/2                unassigned      YES unset  administratively down down   
Ethernet0/3                unassigned      YES unset  administratively down down

 

 

 

 

Comments

  • is your temrserv ethernet port connected to your nic NIO in the .net file?.   If so, r u able to ping ur 169.254.0.1 address sourced from 169.254.0.2 int. ?   

    Sent from my iPhone

    On Nov 23, 2010, at 3:05 PM, crescent1005 <[email protected]> wrote:

     Please help... Two issues

     A) For some reason I cant connect to any hosts from the "TermServ". I am using secureCRT to connect to TermServ however I can telnet directly to Hosts!!

    OS: Windows 7

    TermServ>R1

    Trying R1 (169.254.0.1, 2001)...
    TermServ>sh hosts
    Default domain is not set
    Name/address lookup uses static mappings

    Codes: UN - unknown, EX - expired, OK - OK, ?? - revalidate
           temp - temporary, perm - permanent
           NA - Not Applicable None - Not defined

    Host                      Port  Flags      Age Type   Address(es)
    disalbe                   None  (temp, UN)  0
    R1                        2001  (perm, OK)  0   IP    169.254.0.1
    R2                        2002  (perm, OK)  0   IP    169.254.0.1
    R3                        2003  (perm, OK)  0   IP    169.254.0.1
    R4                        2004  (perm, OK)  0   IP    169.254.0.1
    R5                        2005  (perm, OK)  0   IP    169.254.0.1
    R6                        2006  (perm, OK)  0   IP    169.254.0.1
    SW1                       2007  (perm, OK)  0   IP    169.254.0.1
    SW2                       2008  (perm, OK)  0   IP    169.254.0.1
    SW3                       2009  (perm, OK)  0   IP    169.254.0.1
    SW4                       2010  (perm, OK)  0   IP    169.254.0.1
    BB1                       2011  (perm, OK)  0   IP    169.254.0.1
    BB2                       2012  (perm, OK)  0   IP    169.254.0.1
    BB3                       2013  (perm, OK)  0   IP    169.254.0.1
    disalbe                   NA    (temp, UN)  0  X.121

     

    B) *Mar  1 00:50:20.467: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on Ethernet0/0 (not full duplex), with "remove hostname.doamin" FastEthernet4/35 (full duplex).

    TermServ#sh ip int br
    Interface                  IP-Address      OK? Method Status                Protocol
    Ethernet0/0                169.254.0.2     YES NVRAM  up                    up     
    Ethernet0/1                unassigned      YES unset  administratively down down   
    Ethernet0/2                unassigned      YES unset  administratively down down   
    Ethernet0/3                unassigned      YES unset  administratively down down

     

     

     

     




    Internetwork Expert - The Industry Leader in CCIE Preparation

    http://www.internetworkexpert.com



    Subscription information may be found at:

    http://www.ieoc.com/forums/ForumSubscriptions.aspx
  • Hello johnpgonz, here is my response:

    Is your temrserv ethernet port connected to your nic NIO in the .net file?.  Yes I did that...

    Network Device list output:

    NIO_gen_eth:DeviceNPF_{033BE496-2055-4FA3-8053-960FD65A3C8D}
     Name      : Local Area Connection 3
     Desciption: MS LoopBack Driver

     

    .net File:

    E0/0 = NIO_gen_eth:DeviceNPF_{033BE496-2055-4FA3-8053-960FD65A3C8D}

     

      If so, r u able to ping ur 169.254.0.1 address sourced from 169.254.0.2 int. ? No its not pinging.... Failing both CMD and from TermServ.

    C:>ping 169.254.0.1 -S 169.254.0.2

    Pinging 169.254.0.1 from 169.254.0.1 with 32 bytes of data:
    PING: transmit failed. General failure.
    PING: transmit failed. General failure.

    TermServ#ping 169.254.0.2

    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to 169.254.0.2, timeout is 2 seconds:
    !!!!!
    Success rate is 100 percent (5/5), round-trip min/avg/max = 4/4/4 ms
    TermServ#ping 169.254.0.1 so
    TermServ#ping 169.254.0.1 source 169.254.0.2

    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to 169.254.0.1, timeout is 2 seconds:
    Packet sent with a source address of 169.254.0.2
    .....
    Success rate is 0 percent (0/5)
    TermServ#

     Overall:

    cannot ping the MS loopback from term server
    can ping MS loopback from windows cmd_prompt
    cannot ping Term server from windows cmd_line

     

  • Can you paste the output of a "route print"  from the C prompt and a "show ip route 169.254.0.1"  from TermServ? 

     

    Also from the C prompt are you able to ping the loopback IP, the 169.254.0.1 IP? (not sourcing it w/ another IP)  just a regular ping.


    On Wed, Nov 24, 2010 at 7:46 AM, crescent1005 <[email protected]> wrote:

    Hello johnpgonz, here is my response:

    Is your temrserv ethernet port connected to your nic NIO in the .net file?.  Yes I did that...

    Network Device list output:

    NIO_gen_eth:DeviceNPF_{5135B68F-8236-495E-B92A-A4AE2E1ECF4F}
     Name      : Local Area Connection
     Desciption: Broadcom NetXtreme Gigabit Ethernet Driver

    .net File:

    E0/0 = NIO_gen_eth:DeviceNPF_{5135B68F-8236-495E-B92A-A4AE2E1ECF4F}

     

      If so, r u able to ping ur 169.254.0.1 address sourced from 169.254.0.2 int. ? No its not pinging.... Failing both CMD and from TermServ.

    C:>ping 169.254.0.1 -S 169.254.0.2

    Pinging 169.254.0.1 from 169.254.0.1 with 32 bytes of data:
    PING: transmit failed. General failure.
    PING: transmit failed. General failure.

    TermServ#ping 169.254.0.2

    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to 169.254.0.2, timeout is 2 seconds:
    !!!!!
    Success rate is 100 percent (5/5), round-trip min/avg/max = 4/4/4 ms
    TermServ#ping 169.254.0.1 so

    TermServ#ping 169.254.0.1 source 169.254.0.2

    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to 169.254.0.1, timeout is 2 seconds:
    Packet sent with a source address of 169.254.0.2
    .....
    Success rate is 0 percent (0/5)
    TermServ#

     





    Internetwork Expert - The Industry Leader in CCIE Preparation
    http://www.internetworkexpert.com

    Subscription information may be found at:

    http://www.ieoc.com/forums/ForumSubscriptions.aspx

  • Thx much for quick response...here is the info you need...Also, I dont see 169.254.0.1 configured anywhere on my laptop?  I do see 169.254.206.65 on loopback as seen from CMD Ipconfig /all.  For sure my Ping to 169.254.0.1 is routed to loopback interface 169.254.206.65 and loosing packets there..

    TermServ#sh ip route 169.254.0.1 
    Routing entry for 169.254.0.0/16
      Known via "connected", distance 0, metric 0 (connected, via interface)
      Routing Descriptor Blocks:
      * directly connected, via Ethernet0/0
          Route metric is 0, traffic share count is 1

    TermServ#ping 169.254.206.65                     <--MSFT  Loopback IP as seen from CMD IPconfig.

    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to 169.254.206.65, timeout is 2 seconds:
    .....
    Success rate is 0 percent (0/5)
    TermServ#ping 169.254.0.1  

    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to 169.254.0.1, timeout is 2 seconds:
    .....
    Success rate is 0 percent (0/5)
    TermServ#

     

    From the C prompt, ping is failing to the loopback IP, the 169.254.0.1 IP however I can ping to 169.254.0.2. (not sourcing it w/ another IP)  just a regular ping.

    C:>ping 169.254.0.1

    Pinging 169.254.0.1 with 32 bytes of data:
    Reply from 169.254.206.65: Destination host unreachable.
    Reply from 169.254.206.65: Destination host unreachable.
    Reply from 169.254.206.65: Destination host unreachable.
    Reply from 169.254.206.65: Destination host unreachable.

    Ping statistics for 169.254.0.1:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

    C:>

    C:>ping 169.254.0.2

    Pinging 169.254.0.2 with 32 bytes of data:
    Reply from 169.254.0.2: bytes=32 time=141ms TTL=255
    Reply from 169.254.0.2: bytes=32 time=94ms TTL=255
    Reply from 169.254.0.2: bytes=32 time=50ms TTL=255
    Reply from 169.254.0.2: bytes=32 time=46ms TTL=255

    Ping statistics for 169.254.0.2:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 46ms, Maximum = 141ms, Average = 82ms

     

     

    C:>route print
    ===========================================================================
    Interface List
     22...02 00 4c 4f 4f 50 ......Microsoft Loopback Adapter
     16...00 16 44 cc 90 58 ......Microsoft Virtual WiFi Miniport Adapter
     13...00 1c 23 83 91 d9 ......Broadcom NetXtreme 57xx Gigabit Controller
     12...00 16 44 cc 90 58 ......Dell Wireless 1395 WLAN Mini-Card
      1...........................Software Loopback Interface 1
     18...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2
     14...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
     19...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #3
     20...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #4
     21...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #5
    ===========================================================================

    IPv4 Route Table
    ===========================================================================
    Active Routes:
    Network Destination        Netmask          Gateway       Interface  Metric
              0.0.0.0          0.0.0.0    192.168.1.254    192.168.1.103     25
            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
          169.254.0.0      255.255.0.0         On-link    169.254.206.65    286
       169.254.206.65  255.255.255.255         On-link    169.254.206.65    286
      169.254.255.255  255.255.255.255         On-link    169.254.206.65    286
          192.168.1.0    255.255.255.0         On-link     192.168.1.103    281
        192.168.1.103  255.255.255.255         On-link     192.168.1.103    281
        192.168.1.255  255.255.255.255         On-link     192.168.1.103    281
            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    169.254.206.65    286
            224.0.0.0        240.0.0.0         On-link     192.168.1.103    281
      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    169.254.206.65    286
      255.255.255.255  255.255.255.255         On-link     192.168.1.103    281
    ===========================================================================
    Persistent Routes:
      None

    IPv6 Route Table
    ===========================================================================
    Active Routes:
     If Metric Network Destination      Gateway
      1    306 ::1/128                  On-link
     22    286 fe80::/64                On-link
     12    281 fe80::/64                On-link
     22    286 fe80::a8e0:b92c:c9b7:ce41/128
                                        On-link
     12    281 fe80::f14f:f8d9:5dfc:ad49/128
                                        On-link
      1    306 ff00::/8                 On-link
     22    286 ff00::/8                 On-link
     12    281 ff00::/8                 On-link
    ===========================================================================
    Persistent Routes:
      None

     

     

     

     

  • ok i know what the problem is.  your ip host table is mapping host names to the ip address 169.254.0.1.  So one of two things has to change; the IP of your loopback adapter or you ip host table.  They have to match.  

    hth

    Sent from my iPhone

    On Nov 24, 2010, at 12:24 PM, crescent1005 <[email protected]> wrote:

    here is the info you need...

    TermServ#sh ip route 169.254.0.1
    Routing entry for 169.254.0.0/16
      Known via "connected", distance 0, metric 0 (connected, via interface)
      Routing Descriptor Blocks:
      * directly connected, via Ethernet0/0
          Route metric is 0, traffic share count is 1

    TermServ#ping 169.254.206.65                     <--MSFT  Loopback IP as seen from CMD IPconfig.

    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to 169.254.206.65, timeout is 2 seconds:
    .....
    Success rate is 0 percent (0/5)
    TermServ#ping 169.254.0.1  

    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to 169.254.0.1, timeout is 2 seconds:
    .....
    Success rate is 0 percent (0/5)
    TermServ#

     

    From the C prompt, ping is failing to the loopback IP, the 169.254.0.1 IP however I can ping to 169.254.0.2. (not sourcing it w/ another IP)  just a regular ping.

    C:>ping 169.254.0.1

    Pinging 169.254.0.1 with 32 bytes of data:
    Reply from 169.254.206.65: Destination host unreachable.
    Reply from 169.254.206.65: Destination host unreachable.
    Reply from 169.254.206.65: Destination host unreachable.
    Reply from 169.254.206.65: Destination host unreachable.

    Ping statistics for 169.254.0.1:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

    C:>

    C:>ping 169.254.0.2

    Pinging 169.254.0.2 with 32 bytes of data:
    Reply from 169.254.0.2: bytes=32 time=141ms TTL=255
    Reply from 169.254.0.2: bytes=32 time=94ms TTL=255
    Reply from 169.254.0.2: bytes=32 time=50ms TTL=255
    Reply from 169.254.0.2: bytes=32 time=46ms TTL=255

    Ping statistics for 169.254.0.2:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 46ms, Maximum = 141ms, Average = 82ms

     

     

    C:>route print
    ===========================================================================
    Interface List
     22...02 00 4c 4f 4f 50 ......Microsoft Loopback Adapter
     16...00 16 44 cc 90 58 ......Microsoft Virtual WiFi Miniport Adapter
     13...00 1c 23 83 91 d9 ......Broadcom NetXtreme 57xx Gigabit Controller
     12...00 16 44 cc 90 58 ......Dell Wireless 1395 WLAN Mini-Card
      1...........................Software Loopback Interface 1
     18...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2
     14...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
     19...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #3
     20...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #4
     21...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #5
    ===========================================================================

    IPv4 Route Table
    ===========================================================================
    Active Routes:
    Network Destination        Netmask          Gateway       Interface  Metric
              0.0.0.0          0.0.0.0    192.168.1.254    192.168.1.103     25
            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
          169.254.0.0      255.255.0.0         On-link    169.254.206.65    286
       169.254.206.65  255.255.255.255         On-link    169.254.206.65    286
      169.254.255.255  255.255.255.255         On-link    169.254.206.65    286
          192.168.1.0    255.255.255.0         On-link     192.168.1.103    281
        192.168.1.103  255.255.255.255         On-link     192.168.1.103    281
        192.168.1.255  255.255.255.255         On-link     192.168.1.103    281
            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    169.254.206.65    286
            224.0.0.0        240.0.0.0         On-link     192.168.1.103    281
      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    169.254.206.65    286
      255.255.255.255  255.255.255.255         On-link     192.168.1.103    281
    ===========================================================================
    Persistent Routes:
      None

    IPv6 Route Table
    ===========================================================================
    Active Routes:
     If Metric Network Destination      Gateway
      1    306 ::1/128                  On-link
     22    286 fe80::/64                On-link
     12    281 fe80::/64                On-link
     22    286 fe80::a8e0:b92c:c9b7:ce41/128
                                        On-link
     12    281 fe80::f14f:f8d9:5dfc:ad49/128
                                        On-link
      1    306 ff00::/8                 On-link
     22    286 ff00::/8                 On-link
     12    281 ff00::/8                 On-link
    ===========================================================================
    Persistent Routes:
      None

     

     

     

     




    Internetwork Expert - The Industry Leader in CCIE Preparation

    http://www.internetworkexpert.com



    Subscription information may be found at:

    http://www.ieoc.com/forums/ForumSubscriptions.aspx
  • Can you kinldy elaborate further [w/ a sample configuration template ] as I did not understand! 

    Did you mean I need to statically change MSFT loopback IP 169.254.206.65 to 169.254.0.1 OR On the TermServ, point the HOST's to 169.254.206.65 instead of 169.254.0.1?

     

  • ok, simply put.  You have two options to get it to work.

     

    Option 1.  Change your TCP/IP properties for the NIC to a static ip address of 169.254.0.1 with a subnet mask of 255.255.0.0 .   If you want to put the gateway ip as 169.254.0.2 , that's ok, but it wouldn't hurt to leave no IP at, since you're only communicating locally anyway.


     

    or

     

    Option 2. Modify the existing IP host table.  For example, If you were to do a show run on your TermServ you would see you're table is as such:

     

    ip host R1 2000 169.254.0.1
    ip host R2 2001 169.254.0.1
    ip host R3 2002 169.254.0.1
    ip host R4 2003 169.254.0.1
    ip host R5 2004 169.254.0.1
    ip host R6 2005 169.254.0.1
    ip host SW1 2006 169.254.0.1

    ip host SW2 2007 169.254.0.1
    ip host BB1 2008 169.254.0.1
    ip host BB2 2009 169.254.0.1
    ip host BB3 2010 169.254.0.1

     

    What that table is doing for you is when you type "R1 and then enter", it resolves the name R1 to the IP address 169.254.0.1 .  It's like your a local DNS server so to speak.  But it's called a IP host table.


     

    So your MS Loopback adapter properties have to match your IP host table.  You will not be able to reverse telnet to 169.254.0.1 if it doesn't exist.   It looks to me like you're current MS loop back adapter has the IP address 169.254.206.65  .  That was probably assigned dynamically.  So my suggestion is to statically assign the IP to 169.254.0.1 . After all that is what your host table thinks the IP address is for R1, R2, and so on.  Optionally you can change your IP host table by doing a "config t" then typing "ip host R1 2000 169.254.206.65"  for each device.


     

    Hope this Helps  (HTH)

     

    v/r,
    John

    On Wed, Nov 24, 2010 at 1:10 PM, crescent1005 <[email protected]> wrote:

    Can you kinldy elaborate further [w/ a sample configuration template ] as I did not understand! 




    Internetwork Expert - The Industry Leader in CCIE Preparation
    http://www.internetworkexpert.com

    Subscription information may be found at:

    http://www.ieoc.com/forums/ForumSubscriptions.aspx

  • note that when I said "Option 1.  Change your TCP/IP properties for the NIC"  I meant your MS loopback adapter not your actual ethernet NIC.    Just FYI.  :o)

  • If finally works... Thx much for your quick responses.   Please note ...Yes changed the MS loopback adapter IP to 169.254.0.1/16; did not work. I then added GW 169.254.0.2 ...still did not work. Reloaded my laptop and then finally works. I am just documting this here so someone can benifit :-) and save some time.

     

    Best Regards

     

     

  • cool. no prob.  i like troubleshooting.   enjoy your lab!

    Sent from my iPhone

    On Nov 24, 2010, at 2:33 PM, crescent1005<[email protected]> wrote:

    If finally works... Thx much for your quick responses.   Please note ...Yes changed the MS loopback adapter IP to 169.254.0.1/16; did not work. I then added GW 169.254.0.2 ...still did not work. Reloaded my laptop and then finally works. I am just documting this here so someone can benifit :-) and save some time.

     

    Best Regards

     

     




    Internetwork Expert - The Industry Leader in CCIE Preparation

    http://www.internetworkexpert.com



    Subscription information may be found at:

    http://www.ieoc.com/forums/ForumSubscriptions.aspx
Sign In or Register to comment.