Issue trying to Telnet from W7 64b SP1 to Ubuntu VM in VM Player 12.1.0

[bzdobs]

Just moved a UBUNTU 12.04 VM from XP Pro SP3 to W7 64b SP1 ... had to upgrade to VM Player 12.1.0

Issue: have a character based application running in Ubuntu that requires Telnet access ... in XP Pro with the VM network set to NAT the Ubuntu ifconfig IP address is accessible from XP ... in W7 I have been unable to see the Ubuntu IP address ... Ping fails ... Telnet Fails  ... started from scratch and loaded Ubuntu 14.04 ... still no IP address showing

- Both versions of Ubuntu connect to the internet

- Both versions of Ubuntu can ping the Host IP address

- Both versions immediately crash with BSOD if I choose Bridged OR vNet0 Auto Bridged settings

- Both vNet1 and vNet8 are connected and return Pings

- Norton 360 Firewall and security completely turned off ... still no IP address showing

- Ubuntu 14.04 connects to Windows share from Ubuntu so Samba config is working

- Ubuntu 14.04 telnetd was installed and configured but status indicates server isn't running

sudo apt-get install xinetd telnetd

I am not concerned about Telnet security as this is only being used on a small secure home intranet

Any suggestions would be greatly appreciated

[bzdobs]

NAT connectivity SOLVED ... for whatever reason(s) the installed VM Player VM Networks appear to have been part of the issue. Once the networks were restored to default from vmnetcfg both Telnet and Ping started working  

Telnet Server on Ubuntu

- Ubuntu telnet configuration was definitely incomplete (telnet localhost in ubuntu wasn't even working) ... followed several Telnet threads to get it running properly

- Telnet and Ping from Host W7 still not connecting

VM Networks ... some threads suggested using vmnetcfg.exe to configure the VM Networks

- vmnetcfg.exe apparently used to be located in one of the cab files in past versions of VM Player ... it appears it is not being packaged with 12.1.0

- downloaded VM Workstation Pro 12.1.0 full (installed on another W7 machine)  copied the related vmnetcfg files to a folder on this machine

vmnetcfg.exe

- tried several variations of NAT configurations of VMnet8 ... Wire Shark verified no connections were ever made

- tried adding the host to VMnet0 Bridged

- configured VMnet8 as Bridged ... BSOD occurred (consistent with VM Player Bridged configuration attempts)

- noticed that vmnetcfg has a "restore defaults" button

  after running this restore, the IP subnet changed from 192.168.159.0 to 192.168.43.0 and NOW both the Host Telnet and PING connect to the VM

I have no idea what transpired here ... all threads on this subject suggest this should only work in bridged mode ... my host subnet starts with 10. not 192 so not sure how my router would know to redirect traffic from 10 back to 192 ... or ... why 192.168.159.x doesn't work but 192.168.43.x does

Then there is still the BSOD issue with VMnet8 being Bridged ... if this is supposed to work not sure what to do with this either ... Win7 was a recent fresh install including SP1 and all updates ... the machine was delivered with Win 7 Pro 64b but has been running XP Pro SP3 for several years with VMPlayer 6 and Ubuntu 12.04 with no issues