Trouble connecting with Telnet

Hello everyone... hope all are enjoying the holiday season!

I'm running win7 on my laptop and trying to connect using telnet to the virtual machine on my laptop.  The OS on the virtual machine is XP pro.  Any ideas why this is not happening??  I'm unable to ping either machine from either machine as the request times out.  Any suggestions.

Thanks !

B2 

Forgot to say they both have different IP addresses lol; I have the telnet service started on both my machines as well in case you are wondering.

Thanks,
B2

Also I forgot to mention that both of them are on DHCP and not static.

Thanks,
B2 :0

Could you enter the command "route print" at a command prompt and copy and paste the results here?

Hey Rob,

Here it is


===========================================================================
Persistent Routes:
  None

IPv6 Route Table
===========================================================================
Active Routes:
 If Metric Network Destination      Gateway
 19   1125 ::/0                     2002:c058:6301::c058:6301
  1    306 ::1/128                  On-link
 16     58 2001::/32                On-link
 16    306 2001:0:5ef5:79fd:24da:248b:a9f0:fd8a/128
                                    On-link
 19   1025 2002::/16                On-link
 19    281 2002:560f:275::560f:275/128
                                    On-link
 12    276 fe80::/64                On-link
 16    306 fe80::/64                On-link
 12    276 fe80::18b0:7f39:586f:b636/128
                                    On-link
 16    306 fe80::24da:248b:a9f0:fd8a/128
                                    On-link
  1    306 ff00::/8                 On-link
 16    306 ff00::/8                 On-link
 12    276 ff00::/8                 On-link
===========================================================================
Persistent Routes:
  None


B2

I've deleted content from this as it gave my IP

lol  I know the other one does but I'm going to renew my IP lol  So if you want the "route print" from the virtual machine I can give it to you too.

B2

I've deleted content from this as it gave my IP

That's the bit I needed to see!  You have nothing to fear from revealing your LAN IP address.

Cool, cheers Rob.  Here it is.

===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 03 ff fb a0 bb ...... Intel 21140-Based PCI Fast Ethernet Adapter (Gen
eric) - Packet Scheduler Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0  192.168.131.254  192.168.131.65       20
        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1       1
    192.168.131.0    255.255.255.0   192.168.131.65  192.168.131.65       20
   192.168.131.65  255.255.255.255        127.0.0.1       127.0.0.1       20
  192.168.131.255  255.255.255.255   192.168.131.65  192.168.131.65       20
        224.0.0.0        240.0.0.0   192.168.131.65  192.168.131.65       20
  255.255.255.255  255.255.255.255   192.168.131.65  192.168.131.65       1
Default Gateway:   192.168.131.254
===========================================================================
Persistent Routes:
  None

B2

And could you supplement that with "ipconfig" output from the host and VM?  Ta.

The Host is

Windows IP Configuration


Wireless LAN adapter Wireless Network Connection 2:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . : cable.virginmedia.net
   Link-local IPv6 Address . . . . . : fe80::18b0:7f39:586f:b636%12
   IPv4 Address. . . . . . . . . . . : 86.15.2.117
   Subnet Mask . . . . . . . . . . . : 255.255.252.0
   Default Gateway . . . . . . . . . : 86.15.0.1

Wireless LAN adapter Wireless Network Connection:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Tunnel adapter isatap.{FE2ECAAF-EF55-47BD-A179-EBD795FB2F5C}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Tunnel adapter 6TO4 Adapter:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Tunnel adapter isatap.{F1B11632-A293-45BB-970D-EE41AC9F7251}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Tunnel adapter Reusable Microsoft 6To4 Adapter:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Tunnel adapter Teredo Tunneling Pseudo-Interface:

   Connection-specific DNS Suffix  . :
   IPv6 Address. . . . . . . . . . . : 2001:0:5ef5:79fd:1824:2284:a9f0:fd8a
   Link-local IPv6 Address . . . . . : fe80::1824:2284:a9f0:fd8a%16
   Default Gateway . . . . . . . . . :

Tunnel adapter Local Area Connection* 13:

   Connection-specific DNS Suffix  . : cable.virginmedia.net
   IPv6 Address. . . . . . . . . . . : 2002:560f:275::560f:275
   Default Gateway . . . . . . . . . : 2002:c058:6301::c058:6301

Tunnel adapter isatap.cable.virginmedia.net:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : cable.virginmedia.net

And the VM is

Windows IP Configuration


Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix  . : cable.virginmedia.net
        IP Address. . . . . . . . . . . . : 192.168.131.65
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.131.254


B2

Sorry - I'm still looking for the routing table from the host.  I can see the VM's table and the host's IP6 table only.

I see that you're using a cable modem, so the IP address is actually your WAN address - incorrect assumption on my part.  Feel free to remove it from your posts above, although I still don't consider it to be a particular security risk.  Every script kiddie on the planet already has your IP address. 

By the way - is the firewall on the VM allowing incoming telnet (port 23)?

No I'm having a problem with that.  I'm getting the following message...

Could not open connection to the host, on port 23
: Connect failed

B2

So try disabling the firewall on the XP VM.  Does that make a difference?

I took the firewall down on both.  I'm now getting the message below:

Access Denied: Specified user is not a member of TelnetClients group.
Server administrator must add this user to the above group.

Telnet Server has closed the connection


Connection to host lost.


B2

Well that's pretty straightforward - whichever username you're connecting with, make sure it's a member of that group (or an Administrator).

I'd switch the firewall back on, on the XP VM by the way and just make sure you're allowing incoming port 23 connections.

It's windows 7 home premium I'm using on the laptop.  I tried adding the the local users and groups snap in through mmc.exe and it says it's not valid to be used in this version of windows.  I take it this is a problem then; as I won't be able to add a group with users ??

B2

The error is coming from the XP virtual machine, no?

The Telnet client isn't installed by default on Windows 7. Did you install it?

Why are you using Telnet if you don't know that a local IP is of no consequence privacy-wise? Why not just use remote desktop protocol?

The error is coming from the XP virtual machine, no?

Yup, the error is on the XP VM.

Yup, the error is on the XP VM.

So why are you attempting to edit the W7 users/groups?   

I tried editing on the Win 7 because I was checking for connectivity in both directions.  So I thought maybe if I changed the user/local groups policy in win 7 the vm might connect to this system... as the last error was me trying to connect from vm to the host system.   Connecting from the host system to the vm I still only have the

Could not open connection to the host, on port 23: Connect failed

Sorry for any confusion.

B2

Could not open connection to the host, on port 23: Connect failed

I thought we'd eliminated this by opening the XP firewall?

Hey Rob.

Sorry for the mega late reply.  Yeah once the firewall was down I got a reply.  I'll have to revisit this one soon me things as I'm doing a cisco course at night as well as my college during the day.  Had a few personal probs also, so again I'm really sorry for the late response.  I'll prob need your help in the future with this one lolz.
 
I'm going to put this one on hold for the time being though; as things are getting a bit hectic with college and stuff, so all my time is there at the mo.

Thanks again!!

B2

No problem.  Whenever you're ready.

I might be completely off here...

But Windows 7 is using IPv6 ... Windows XP doesn't do IPv6 as standard does it?

I think the problem here is the firewall, rather than the routing protocol.  The hypervisor will almost certainly be routing IPv4 in both directions.