Troubles using PuTTY to connect to newly created Linux VM

thepixelgeek

Patron
Joined
Jan 21, 2016
Messages
271
I can access my VM using the VNC viewer, but I'd like to use PuTTY to SSH into my VM.

Do I need to be using the VNC Port #?
Does it matter my computer is on a different network 192.168.4.x? I'm not sure why the VM was assigned 192.168.7.x??
  • SSH is turned on under Freenas services
  • I confirmed IP address to be 192.168.7.74
  • Server is listening on port 22
  • ssh.service says "active (running)

PuTTY settings:
Host: 192.168.7.74
Port: 22
Type: SSH

VM:
Linux > Ubuntu Server 18
 
Last edited:

Kcaj

Contributor
Joined
Jan 2, 2020
Messages
100
Im not sure if bhyve has a way to access a VM through SSH but it sounds like you will actually need to configure SSH on the VM first then connect with your putty settings. i.e configure SSH in ubuntu

Does it matter my computer is on a different network 192.168.4.x? I'm not sure why the VM was assigned 192.168.7.x??

Do you have VLAN's configured in your network? You will need to be able to communicate with the .7 subnet to be able to connect via SSH to the VM.
 
Last edited:

thepixelgeek

Patron
Joined
Jan 21, 2016
Messages
271
Pretty sure I've enabled ssh in ubuntu...especially since it says "ssh.service active (running).

Do you have VLAN's configured in your network? You will need to be able to communicate with the .7 subnet to be able to connect via SSH to the VM.
No VLANs here.
 

Kcaj

Contributor
Joined
Jan 2, 2020
Messages
100
So you can ping the IP of the VM? Can you ping your other host from inside the VM?

Pretty sure I've enabled ssh in ubuntu...especially since it says "ssh.service active (running).

What does a command like nmap -p 22 192.168.7.74 tell you from outside your VM?
 

thepixelgeek

Patron
Joined
Jan 21, 2016
Messages
271
So you can ping the IP of the VM? Can you ping your other host from inside the VM?
Yes, I can ping it from Windows cmd.

1582057198270.png


What does a command like nmap -p 22 192.168.7.74 tell you from outside your VM?
nmap is not recognized
 
Last edited:

thepixelgeek

Patron
Joined
Jan 21, 2016
Messages
271
Last edited:

thepixelgeek

Patron
Joined
Jan 21, 2016
Messages
271
What does telnet 192.168.7.74 22 say?
Same. Using windows machine command line. Says, "Not recognized as an internal or external command."
 

Fredda

Guru
Joined
Jul 9, 2019
Messages
608

thepixelgeek

Patron
Joined
Jan 21, 2016
Messages
271
Last edited:

thepixelgeek

Patron
Joined
Jan 21, 2016
Messages
271
telnet was black screen, no info.
 

Kcaj

Contributor
Joined
Jan 2, 2020
Messages
100
Did you try the section under "Verifying that the telnet client is enabled" or "Already have telnet installed but still failing?" from the link that @Fredda so kindly provided?
 

thepixelgeek

Patron
Joined
Jan 21, 2016
Messages
271
Did you try the section under "Verifying that the telnet client is enabled" or "Already have telnet installed but still failing?"
Yes, telnet is confirmed.
1582072030805.png
 

Kcaj

Contributor
Joined
Jan 2, 2020
Messages
100
Did you type [22]?

Can you try without the square brackets? i.e telnet 192.168.7.74 22 It could just be the windows formatting though.

Edit: Otherwise you need to check the firewall and or router settings as since you can ping the host, it seems like port 22 is blocked. That could be on the VM, the windows machine or a device routing between .4 & .7 subnets
 
Last edited:

Fredda

Guru
Joined
Jul 9, 2019
Messages
608
Code:
Microsoft Telnet> help

Commands may be abbreviated. Supported commands are:

c    - close                    close current connection
d    - display                  display operating parameters
o    - open hostname [port]     connect to hostname (default port 23).

You should make yourself aquainted with some general naming conventions in computer commands.
In this context the "[]" around the port parameter does not mean they should be typed, but rather this parameter is an optional one, which can be omitted if it is not needed.
 

thepixelgeek

Patron
Joined
Jan 21, 2016
Messages
271

thepixelgeek

Patron
Joined
Jan 21, 2016
Messages
271
Otherwise you need to check the firewall and or router settings as since you can ping the host, it seems like port 22 is blocked. That could be on the VM, the windows machine or a device routing between .4 & .7 subnets
Appears so. Thanks.
 
Top