VMWARE Linux Issue to connect with Putty

[AbdulDBA]

Hi All,

I am trying to transfer files from my Windows 7 machine into my VMware OEL 5 .

But i am not able to connect the Filezillah and not even able to login with Putty also.

About my System

1. My network is a normal one not having any domain and all, just a normal broadband modem so my IP is not a static IP [192.168.1.4]

2. My VM is a Fresh installed and it obtain the IP automatically [192.168.1.22]

3. In VM ware BRIDGE is enabled from the begging.

4. LINUX and WINDOWS can able to ping vice verse

5. Both Firewalls are Disabled

6. I am trying to connect a 64bit[Linux server in VMWARE] server from 32bit windows OS, will this may be a issue ??

Kindly advice me what are the other options i have to check to connect my Putty to Linux Server and how do i transfer files to my linux box via filezilla..

Message was edited by: Wil van Antwerpen Removed blue background on text so that it is readable

[louyo]

Set up (install if necessary) Samba server in your Linux server and then map a drive to the share(s).

Putty lets you SSH into the Linux machine but I think there are better ways.

You could set up shared folders to your host and access them via /mnt/hgfs but that can be unreliable, in my experience.

I use Samba with mapped drives from the Windows box (VM) to Linux

or going the other way around

use smb://<ipaddressofhost>/<sharename> from the Linux box to the Windows box (VM). I use konqueror for that but you can also install and use an smb client.

Lou

[continuum]

Most probable explanation: sshd on the OEL5 is not running.
Try to connect to port 22 with telnet to check if anything is listening at all

[AbdulDBA]

Hi Continuum,

Yes SSHD service is running,,

And also i am trying to connect with port 22 ..

Pls advice ..

Regards

Hamid

[wila]

Hi Abdul,

Not sure what your routes are with the extra bridge in there. One slipup there and your SSH becomes unreachable.

Also Continuum asked if you could try to connect with telnet, eg:

C:\>telnet 192.168.1.22 22

you should see something like:

SSH-2.0-OpenSSH_5.9

followed up by a blinking cursor.

--

Wil

[AbdulDBA]

Hi Wili,

pls check this below screen shorts,, i tried to connect with telnet by putty

There is no important in my simple TEST configuration .

Hope this is the method u wanted me to test or any other commend line method available,, i mean from my host machine to guest machine via cmd prompt.. ??

[WoodyZ]

In your OP you said the IP Address was 192.168.1.22 however you're now testing with 192.168.1.34, so has the IP Address actually changed?

Also if the Host and Guest can ping each other in Bridged mode then if sshd is running and you're validating with proper credentials then you should be able to connect.

Have you tried using NAT?

BTW I tested with PuTTY from my Mac using Wine and XQuartz to run it and connected to an RHEL VM without any issue so it should pretty much work out of the box if you've disabled the Firewalls, enabled sshd and use proper credentials.

[WoodyZ]

Also just notice you used Port 23 on the Telnet test and Wil said to use Port 22.

Thy it using Port 22 and see if it returns something like "SSH-2.0-OpenSSH_5.3" and note the output shown here may differ slightly from yours if it completes successfully.

[wila]

Hi user,

Woody did kind of spell it out already, but ... just to make sure, some background.

Normally you do not have a telnet server running (port 23), my request for the telnet test was to actually run the program "telnet" from a command line (sometimes also -incorrectly- referred to as a "dosbox") not in PuTTY. Running that from PuTTY isn't much help.

Please note that in newer versions of Windows you have to actually get the telnet client (NOT the server) by enabling a windows feature.

The last parameter on the telnet command is the port number, port 22.

SSH by default always uses port 22 so unless you changed that, that's the port to test for.

The telnet test is a very basic networking test, just like ping and is often used to see if a particular service is running and accessible on the host you are trying to access.

Normally it will return the banner of the service that you are trying to access. The banner we expect to see is the one from SSH (as mentioned at my earlier reply)

If that doesn't give anything try running the following commands (command line now in linux and as root)

netstat -tulpen | grep -i ssh

and post the output back.

Also make sure that you are accessing the correct IP address of the linux guest:

Please also post output from (also run as root)

ifconfig | grep addr

--

Wil

[WoodyZ]

wila wrote: Normally you do not have a telnet server running (port 23), my request for the telnet test was to actually run the program "telnet" from a command line (sometimes also -incorrectly- referred to as a "dosbox") not in PuTTY. Running that from PuTTY isn't much help.

Wil, I saw you were using a Command Prompt in your previous reply however the test is still valid with PuTTY when selecting Telnet and changing to Port 22, it will return the banner in the TTY.

[wila]

Thanks Woody, I do use PuTTY, but never as telnet client, pretty sure I still prefer cli. but good to know that the telnet client in PuTTY is working as it should.

--

Wil

[WoodyZ]

If Telnet is installed then I too prefer to use it directly from Command Line however using PuTTY to test for a response still does it from the TTY (CLI), it just starts up with a GUI and AbdulDBA should get a valid response either way if all is okay.

[AbdulDBA]

Hi Wili,

Thanks for your help,,

Yes i refered how to check the telnet,, by this following site :How to Activate Telnet in Windows 7: 9 Steps - wikiHow

And enabled the telnet server and telnet client. i logged in to telnet service and checked the status it says : NOT CONNECTED..

Again i tried to ping by telnet

C:\Users\User>telnet 192.168.1.34

Connecting To 192.168.1.34...Could not open connection to the host, on port 23: Connect failed

Then i tried to open the port by issuing the following commend

Microsoft Telnet> open 192.168.1.34

Connecting To 192.168.1.34...Could not open connection to the host, on port 23: Connect failed

Microsoft Telnet> open 192.168.1.34 23

Connecting To 192.168.1.34...Could not open connection to the host, on port 23: Connect failed

I am Still alive,, but problem not solved,, just because of Timezone my reply is late

Regards

[AbdulDBA]

Not Ok yet.. just trying to open the port as willi instructed.. am working on that at this early morning 3.56AM  :smileyblush:

[AbdulDBA]

AS per your instruction i issued this below commends on OEL Terminal as root user:

[wila]

Hi @AdbulDBA

Details are important. Only asked for installing telnet client, if you installed telnet server and started the telnet server service, then do stop it and shut it down. No need for a telnet server running.

Your IP address in there is correct, but you forgot adding the port for ssh.

Do note that we're still just testing if the port of the SSH server can be reached.

It should have been:

C:\Users\User>telnet 192.168.1.34 22

SSH runs on port 22 on your linux server.

--

Wil

[continuum]

Maybe openssh is setup using strict mode and it just will not allow connections from your host because the saved keys are no longer valid.
It may help to uninstall openssh and remove all existing saved hostkeys.

[AbdulDBA]

Result from Linux Box.. Hope ssh running on the same port 22.. no issues from Linux Box

Result for Telnet from my host machine,, Note my telnet server and telnet clients are started by Turn Windows Features On or Off option in the host machine

but i could not able to connect the guest linux via telnet !!

Mr.continuum kindly instruct me how to enable the openssh keys ?

[AbdulDBA]

Hi,

I installed openSSH by a youtube instruction. but not able to connect with the linux

I hope SSH is running is in it ?~?~

Pls Advice Mr.wila & Mr.Continuum

[wila]

@Continuum,

Telnet would still be able to connect on port 22 and the banner would display even if you set keys.

He's getting a time out as if he has a firewall running on the linux host blocking ssh.

--

Wil