Ok after a lot of reading and messing around I found and learned out to use PFsensese. I have a server 2003 running and a xp work station both adapaters are set on internal. I have a pfsense wih 2 adapaters 1. Bridged and 1 internal.
Now the work station and the server can ping each other and the pfsense
Workstation ip info is
10.1.10.50
255.255.255.0
10.1.10.1
server is
10.1.10.13
255.255.255.0
10.1.10.1
the pfsense has a WAN of 192.168.1.14(DHCP)
and a lan 10.1.10.1
I would like both computer to get internet access. But as of right now they cant
My Host machine is connect to a dsl/router via a cat5 cable. My ip settings for the host are 192.168.1.2 and the gateway is 192.168.1.1 255.255.255.0
I dont know if this means anything but when i got into my network control panel on the host I see another connection. VB host only network which it says it has no access?? Am i suspose to set up a static ip on this becaue it looksl ike the ip is wrong 192.168.56.1 and it doesnt even have a gate way put in.. I dont want to mess with that unless i know thats the problem. Once more thing is the virtual box bridged driver suspose to be check in any of the two adapaters? It is checked on my nic but not on the VB adapater.
Thanks
Netwrok help (again)
-
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: Netwrok help (again)
If you are not using the Host Only interface on the host, you can safely disable it.
If your server is not a DC, you can simply enable NAT on the PFSense router to give your internal network Internet access.
If it is a DC, things are a bit more complex, but that is a Windows matter, not VirtualBox.
If your server is not a DC, you can simply enable NAT on the PFSense router to give your internal network Internet access.
If it is a DC, things are a bit more complex, but that is a Windows matter, not VirtualBox.
Bill