[Solved] Networking issues
-
GavinBaumanis
- Posts: 5
- Joined: 23. Jun 2013, 20:29
[Solved] Networking issues
Hi there,
I have read the Networking FAQ and also done a search but can;t seem to find what I am looking - which surprises me a little because I can;t believe I am the first to have this issue...
Anyway,
I have Mac 10.8.4 as the Host
and I have Windows 7 64-bit as the Guest.
and I am using Virtual Box 4.2.14
The short of it is - I have MS-SQL installed on the windows 7 guest and would like to access it from the Host (Mac).
I am attempting to get everything working in Bridged-mode.
Because I am also using the VM for accessing other MS-SQL servers using the Guest OS's SQL Server Manager.
Lastly - and unrelated;
If I choose "host-only" I get told that I have chosen an invalid setting and cannot click OK.
As always - Thanks in advance.
- Gavin
I have read the Networking FAQ and also done a search but can;t seem to find what I am looking - which surprises me a little because I can;t believe I am the first to have this issue...
Anyway,
I have Mac 10.8.4 as the Host
and I have Windows 7 64-bit as the Guest.
and I am using Virtual Box 4.2.14
The short of it is - I have MS-SQL installed on the windows 7 guest and would like to access it from the Host (Mac).
I am attempting to get everything working in Bridged-mode.
Because I am also using the VM for accessing other MS-SQL servers using the Guest OS's SQL Server Manager.
Lastly - and unrelated;
If I choose "host-only" I get told that I have chosen an invalid setting and cannot click OK.
As always - Thanks in advance.
- Gavin
Last edited by GavinBaumanis on 3. Jul 2013, 09:53, edited 1 time in total.
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Mostly XP
Re: Networking issues
You have said what you're trying to do, but not what your problem is.
-
GavinBaumanis
- Posts: 5
- Joined: 23. Jun 2013, 20:29
Re: Networking issues
I cannot connect to the SQL server on the guest from the host.
-
noteirak
- Site Moderator
- Posts: 5231
- Joined: 13. Jan 2012, 11:14
- Primary OS: Debian other
- VBox Version: OSE Debian
- Guest OSses: Debian, Win 2k8, Win 7
- Contact:
Re: Networking issues
Can you ping or connect with any other program to the guest from the host? Did you disable firewalls & stuff?
Hyperbox - Virtual Infrastructure Manager - https://apps.kamax.lu/hyperbox/
Manage your VirtualBox infrastructure the free way!
Manage your VirtualBox infrastructure the free way!
-
BillG
- Volunteer
- Posts: 5106
- Joined: 19. Sep 2009, 04:44
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows 10,7 and earlier
- Location: Sydney, Australia
Re: Networking issues
Have you set the guest to use bridge mode? Does it have an IP in the same IP subnet as the machine you are seeking to contact it from? If in doubt, post an ipconfig of each machine.
Bill
-
GavinBaumanis
- Posts: 5
- Joined: 23. Jun 2013, 20:29
Re: Networking issues
Thanks everyone - and sorry for the delay...
I "think" I have a better understanding of the issue - but of course being completely new to VB - could be wrong!
At (my personal) home my Host, get s a 10.0.2.xxx private address.
I have port forwarded 127..0.0.1:1433 to 10.0.2.15:1433 - and so at home it works like a charm.
At work it gets a 192.168.x.x address.
The guest OS (seemingly) always gets a 10.0.2.15 address regardless - which places it (at work) in a different IP range.
So I think this is why I am not connecting to my SQL server when at work.
That's the information I have... not sure if it helps or not...
The network is set up for NAT.
Here is the ifconfig from the problematic host (at work);
Here is the IPconfig from the guest;
I suppose what I need to know is how do I ensure that my host and guest are always on the same static LAN so that I can set an appropriate port forward rule?
Or is there a way to do this dynamically, so that it doesn't matter what IP Address the Host gets?
As always - thanks very much for your help - I do appreciate it.
Gavin.
I "think" I have a better understanding of the issue - but of course being completely new to VB - could be wrong!
At (my personal) home my Host, get s a 10.0.2.xxx private address.
I have port forwarded 127..0.0.1:1433 to 10.0.2.15:1433 - and so at home it works like a charm.
At work it gets a 192.168.x.x address.
The guest OS (seemingly) always gets a 10.0.2.15 address regardless - which places it (at work) in a different IP range.
So I think this is why I am not connecting to my SQL server when at work.
That's the information I have... not sure if it helps or not...
The network is set up for NAT.
Here is the ifconfig from the problematic host (at work);
Code: Select all
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
options=3<RXCSUM,TXCSUM>
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=2b<RXCSUM,TXCSUM,VLAN_HWTAGGING,TSO4>
ether 10:dd:b1:a1:01:46
inet6 fe80::12dd:b1ff:fea1:146%en0 prefixlen 64 scopeid 0x4
inet 192.168.91.222 netmask 0xffffff00 broadcast 192.168.91.255
media: autoselect (1000baseT <full-duplex,flow-control>)
status: active
en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether 4c:8d:79:e4:c4:10
inet6 fe80::4e8d:79ff:fee4:c410%en1 prefixlen 64 scopeid 0x5
inet 192.168.91.233 netmask 0xffffff00 broadcast 192.168.91.255
media: autoselect
status: active
fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 4078
lladdr 10:dd:b1:ff:fe:68:8a:7e
media: autoselect <full-duplex>
status: inactive
p2p0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 2304
ether 0e:8d:79:e4:c4:10
media: autoselect
status: inactiveHere is the IPconfig from the guest;
Code: Select all
Windows IP Configuration
Host Name . . . . . . . . . . . . : GavinBaumanis
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : internode.on.net
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : internode.on.net
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Desktop Adapter
Physical Address. . . . . . . . . : 08-00-27-E1-2D-7B
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::589d:385e:ddc7:cba5%11(Preferred)
IPv4 Address. . . . . . . . . . . : 10.0.2.15(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Wednesday, 3 July 2013 1:25:57 PM
Lease Expires . . . . . . . . . . : Thursday, 4 July 2013 1:25:57 PM
Default Gateway . . . . . . . . . : 10.0.2.2
DHCP Server . . . . . . . . . . . : 10.0.2.2
DHCPv6 IAID . . . . . . . . . . . : 235405351
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-59-0A-5D-08-00-27-E1-2D-7B
DNS Servers . . . . . . . . . . . : 192.168.91.253
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter isatap.internode.on.net:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : internode.on.net
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 11:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:9d38:953c:3892:3512:f5ff:fdf0(Preferred)
Link-local IPv6 Address . . . . . : fe80::3892:3512:f5ff:fdf0%12(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : DisabledOr is there a way to do this dynamically, so that it doesn't matter what IP Address the Host gets?
As always - thanks very much for your help - I do appreciate it.
Gavin.
-
noteirak
- Site Moderator
- Posts: 5231
- Joined: 13. Jan 2012, 11:14
- Primary OS: Debian other
- VBox Version: OSE Debian
- Guest OSses: Debian, Win 2k8, Win 7
- Contact:
Re: Networking issues
If that's what you've put in Virtualbox NAT forwarding rules, remove the IPs completely, and only keep the ports.GavinBaumanis wrote:I have port forwarded 127..0.0.1:1433 to 10.0.2.15:1433
Then from your host, you should be able to use 127.0.0.1:1433
Hyperbox - Virtual Infrastructure Manager - https://apps.kamax.lu/hyperbox/
Manage your VirtualBox infrastructure the free way!
Manage your VirtualBox infrastructure the free way!
-
GavinBaumanis
- Posts: 5
- Joined: 23. Jun 2013, 20:29
Re: Networking issues
Hi Again - and thanks for the help.
Removing all IPs (Host and Guest)
And just having port 1433 -> 1433
I have restarted the Guest (and even the host) after making the changes.
But... unfortunately I am still unable to connect to the SQL Server from the host to the guest.
I simply get a network timeout error.
Do I still have the network set as NAT?
reading the docs - I would have thought that I wanted "host-only" as the Network choice - but I get told it is an invalid choice.
As always thanks!
Gavin.
I have altered the port forwarding rules as you suggested;noteirak wrote:If that's what you've put in Virtualbox NAT forwarding rules, remove the IPs completely, and only keep the ports.GavinBaumanis wrote:I have port forwarded 127..0.0.1:1433 to 10.0.2.15:1433
Then from your host, you should be able to use 127.0.0.1:1433
Removing all IPs (Host and Guest)
And just having port 1433 -> 1433
I have restarted the Guest (and even the host) after making the changes.
But... unfortunately I am still unable to connect to the SQL Server from the host to the guest.
I simply get a network timeout error.
Do I still have the network set as NAT?
reading the docs - I would have thought that I wanted "host-only" as the Network choice - but I get told it is an invalid choice.
As always thanks!
Gavin.
-
GavinBaumanis
- Posts: 5
- Joined: 23. Jun 2013, 20:29
Re: Networking issues
For all those that replied - thanks for your help.
I have solved my issue.
Once I altered the port forward rules to just be for the PORT only, from a VB perspective, it was all working fine and dandy.
The solution to my connection issue was ensuring as appropriate rule was in place for the Windows Firewall to allow connections for port 1433.
Again - thanks for all your help!
Gavin
I have solved my issue.
Once I altered the port forward rules to just be for the PORT only, from a VB perspective, it was all working fine and dandy.
The solution to my connection issue was ensuring as appropriate rule was in place for the Windows Firewall to allow connections for port 1433.
Again - thanks for all your help!
Gavin