VirtualBox Networking

I am trying to setup a lab to test Exchange Server. I am running Exchange Server on a VirtualBox virtual machine.

On the virtual machine, I have selected Bridged networking. I can get to the internet, can ping my host machine, router, etc.

My host machine is 192.168.1.10 and the virtual machine is 192.168.1.51.

I setup port forwarding on my router/firewall to forward port 25 to the virtual machine's ip. I also have public dns pointed to the external ip of my router/firewall.

I tried a telnet <my domain name> 25 and it failed. I also tried telnetting from my host machine on the same subnet. That failes to. If I run the telnet command on the Exchange server itself, it responds, so it is listening on port 25.

Since I can't telnet from the host machine, I think it must be something to do with the way I have networking setup on the virtual machine.

By the way, Windows Firewall is disabled on all machines.



adam2112Asked:
Who is Participating?
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
thats very odd, bridged networking should forward packets without filtering.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
are you sure this is Bridged and not NAT?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
when you tried telnet on the Exchange server, did you try telnet 127.0.0.1 25 and it's ip address telnet 192.168.1.51 25?

both work?
0
Network Scalability - Handle Complex Environments

Monitor your entire network from a single platform. Free 30 Day Trial Now!

 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
hang on, are we using hostnames or ip addresses here?

try IP addresses with telnet?
0
 
adam2112Author Commented:
It is bridged.

From the Exchange Server I did a telnet to 127.0.0.1 but not 192.168.1.51.

From a remote pc I tried it by my registered DNS name that points to the public ip of my firewall. The firewall has port forwarding for port 25 that directs it to 192.168.1.51.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
if you telnet 192.168.1.51 25 do get a connection?
0
 
adam2112Author Commented:
Tried telnetting from the Exchange server using telnet 192.168.1.51 25 and it was successful, too.
0
 
adam2112Author Commented:
This is kinda strange. I shutdown the virtual machine, changed it to NAT, rebooted, shutdown, and changed it back to Bridged and now it's working in all scenarios.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
sounds like it was in NAT, bit of a bug.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
glad its all working, you running virtualbox 4.0.6?
0
 
adam2112Author Commented:
Yep. 4.0.6
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.