Trouble connecting host to client
Trouble connecting host to client
Hi all,
I've been struggling with this problem for several weeks.
I need my windows host to communicate to my Ubuntu client.
I've disabled firewalls, and performed the apropriate host only connection but cannot get the two to communicate.
I can connect on the ubuntu box localy through SSH, but cannot connect from the windows host with putty. Putty does work on other remote systems
here is the output from VBoxManage list hostonlyifs
Name: VirtualBox Host-Only Ethernet Adapter #2
GUID: 9137eba4-4ec8-4895-8ac0-b47671478bd1
DHCP: Disabled
IPAddress: 192.168.239.1
NetworkMask: 255.255.255.0
IPV6Address: fe80:0000:0000:0000:c4d3:7431:c9d9:ecfe
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 08:00:27:00:24:a9
MediumType: Ethernet
Status: Up
VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #
2
Name: VirtualBox Host-Only Ethernet Adapter
GUID: faa4b3c1-7603-46f2-a685-27ece17ab4bb
DHCP: Disabled
IPAddress: 192.16.56.1
NetworkMask: 255.255.255.0
IPV6Address: fe80:0000:0000:0000:41d0:50ac:d43c:eeb1
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 08:00:27:00:10:c1
MediumType: Ethernet
Status: Up
VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter
Any advice would be greatly appreciated.
I've been struggling with this problem for several weeks.
I need my windows host to communicate to my Ubuntu client.
I've disabled firewalls, and performed the apropriate host only connection but cannot get the two to communicate.
I can connect on the ubuntu box localy through SSH, but cannot connect from the windows host with putty. Putty does work on other remote systems
here is the output from VBoxManage list hostonlyifs
Name: VirtualBox Host-Only Ethernet Adapter #2
GUID: 9137eba4-4ec8-4895-8ac0-b47671478bd1
DHCP: Disabled
IPAddress: 192.168.239.1
NetworkMask: 255.255.255.0
IPV6Address: fe80:0000:0000:0000:c4d3:7431:c9d9:ecfe
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 08:00:27:00:24:a9
MediumType: Ethernet
Status: Up
VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #
2
Name: VirtualBox Host-Only Ethernet Adapter
GUID: faa4b3c1-7603-46f2-a685-27ece17ab4bb
DHCP: Disabled
IPAddress: 192.16.56.1
NetworkMask: 255.255.255.0
IPV6Address: fe80:0000:0000:0000:41d0:50ac:d43c:eeb1
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 08:00:27:00:10:c1
MediumType: Ethernet
Status: Up
VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter
Any advice would be greatly appreciated.
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Trouble connecting host to client
Host 1
IPAddress: 192.168.239.1
host 2
IPAddress: 192.16.56.1
But you don't say what the guest uses
IPAddress: 192.168.239.1
host 2
IPAddress: 192.16.56.1
But you don't say what the guest uses
Re: Trouble connecting host to client
My apologies
Host 1
IPAddress: 192.168.239.10
host 2
IPAddress: 192.16.56.10
Host 1
IPAddress: 192.168.239.10
host 2
IPAddress: 192.16.56.10
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Trouble connecting host to client
Assuming that these are the guests IP then you need to clarify which one does not work. These are different subnets so the host and guest subnets must be the same.
Re: Trouble connecting host to client
I know it's confusing,
In my many items to try out, was another virtual network device.
They both speak to the same client.
In my many items to try out, was another virtual network device.
They both speak to the same client.
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Trouble connecting host to client
In that case without a flow chart and exact IP information on the guests it will be impossible to help remote.
Re: Trouble connecting host to client
Understood.
I can remove the #2 from the system. This would bring it back to the original configuration, wish also had the same problem. Is that satisfactory?
I can remove the #2 from the system. This would bring it back to the original configuration, wish also had the same problem. Is that satisfactory?
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Trouble connecting host to client
Sure. I also see that you have disabled the dhcp server of the host-only network. Any real reason to do that?
Re: Trouble connecting host to client
That is odd. in the gui it says it's enabled.
Here is the update.
Name: VirtualBox Host-Only Ethernet Adapter
GUID: faa4b3c1-7603-46f2-a685-27ece17ab4bb
DHCP: Disabled
IPAddress: 192.16.56.1
NetworkMask: 255.255.255.0
IPV6Address: fe80:0000:0000:0000:41d0:50ac:d43c:eeb1
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 08:00:27:00:10:c1
MediumType: Ethernet
Status: Up
VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter
Here is the update.
Name: VirtualBox Host-Only Ethernet Adapter
GUID: faa4b3c1-7603-46f2-a685-27ece17ab4bb
DHCP: Disabled
IPAddress: 192.16.56.1
NetworkMask: 255.255.255.0
IPV6Address: fe80:0000:0000:0000:41d0:50ac:d43c:eeb1
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 08:00:27:00:10:c1
MediumType: Ethernet
Status: Up
VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Trouble connecting host to client
Something is not right. the address should be 192.168.56.1 (default) from the host and dhcp enabled.
See SS of the default values below.
See SS of the default values below.
Re: Trouble connecting host to client
k, I set it up exactly as indicated above, with the only exception is IPV6 is disabled and could not put 0 on the mask lenght.
I even removed the ethernet device and recreated it. DHCP still shows dissabled on hostonlyIFS BUT shows it working on dhcpserver. Regardless. my ip address for my client is 192.168.58.101. and still cannot connect from the host.
NetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter
IP: 192.168.58.100
NetworkMask: 255.255.255.0
lowerIPAddress: 192.168.58.101
upperIPAddress: 192.168.58.254
Enabled: Yes
"\Program Files\Oracle\VirtualBox"\VBoxManage list hostonlyif
Name: VirtualBox Host-Only Ethernet Adapter
GUID: f25418b1-88f0-42af-97cd-22514eb78281
DHCP: Disabled
IPAddress: 192.168.58.1
NetworkMask: 255.255.255.0
IPV6Address: fe80:0000:0000:0000
a4fc:f7b6:e241
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 08:00:27:00:b0:3b
MediumType: Ethernet
Status: Up
VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter
I even removed the ethernet device and recreated it. DHCP still shows dissabled on hostonlyIFS BUT shows it working on dhcpserver. Regardless. my ip address for my client is 192.168.58.101. and still cannot connect from the host.
NetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter
IP: 192.168.58.100
NetworkMask: 255.255.255.0
lowerIPAddress: 192.168.58.101
upperIPAddress: 192.168.58.254
Enabled: Yes
"\Program Files\Oracle\VirtualBox"\VBoxManage list hostonlyif
Name: VirtualBox Host-Only Ethernet Adapter
GUID: f25418b1-88f0-42af-97cd-22514eb78281
DHCP: Disabled
IPAddress: 192.168.58.1
NetworkMask: 255.255.255.0
IPV6Address: fe80:0000:0000:0000
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 08:00:27:00:b0:3b
MediumType: Ethernet
Status: Up
VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Trouble connecting host to client
Host-only will only allow the guest and host to talk between themselves, and no one else can access the guest.
If you can not access the host><guest then check the firewalls.
If you can not access the host><guest then check the firewalls.