Virtual Machine Troubles
I had a sever up and running and fully functional and I wanted to move it to a virtual machine so I did. Now I cannot connect to the everquest server on the pc running the virtual machine. I keep getting 1017. Ive looked at all the NAT fixes and I think it is just a simple matter of not putting in the appropriate lines in the hosts file.
Here is my ipconfig maybe someone can tell me what to put in hosts. If it isnt the hosts file then im lost. Code:
Microsoft Windows [Version 6.1.7600] |
I thought the purpose of a virtual enviroment was to isolate that enviroment from the rest of the machine in order to prevent it from being harmed. If the two enviroments can interact freely it would defeat the point of the virtual enviroment. I am certainly not an expert in virtual machines but that was my understanding of the subject.
|
I run EQEmu on a Linux virtual machine with no problems. I use VirtualBox and have been for many years, with Minilogin as well.
Use bridging so that the VM is in the same subnet as your PC. Your VM NICs show as 192.168.116.1 & 192.168.142.1 but your PC is 192.168.1.7. NAT places the VM in its own subnet which is probably more work to get working than anything else, if it is even possible. I tried changing the subnet mask so that both networks were part of the same network etc... but couldn't get it to work. When I switched to bridging it was like magic. With a Class C subnet (255.255.255.0) the first 3 octets of the IPs (the 255) you use should be the same (e.g. 192.168.1.x). Also, give your VM a static IP so it doesn't change on you. I also had to open up the appropriate ports on the VM's firewall. Good luck. |
To be honest it would be really great if anyone could point me to a walkthrough on making a bridge work. I am new to virtual machines and networking. I would really like to get the server up an running because I have several zones built that I would like to debut. The reasoni the server is on a virtual machine is that I need to let my best friend be able to remote into it without afffecting whatever work I may be doing on my pc and I want to be able to play everquest from my real pc rather then having to use the virtual machine to play.
Real PC ipconfig Code:
Microsoft Windows [Version 6.1.7600]Code:
Microsoft Windows [Version 6.1.7600] |
As LeftRoad mentioned, your best and easiest way to fix your problem is to put your VM on the same IP subnet as your host machine.
Place your VM on the same subnet by changing your VMnet1 and VMnet8 adapters to be on the same subnet (or enable them to use DHCP if you don't mind the IP address changing). By the sounds of it though you would want to use a static IP address though since you have somebody else remoting into your network from the outside. What this means is you have to set your VMnet adapters to be in the "192.168.1.xxx" range where xxx is a unique number between 2 and 254. Notice below that your VMnet adapters have IP addresses of 192.168.116.1 and 192.168.142.1 and Dustin-PC has an IP address of 192.168.1.7. These will not communicate with one another unless you have some routing help because they are on different networks. In basic terms for home use, all of your computers (and home router) should have the same first 3 octets (192.168.1.xxx) or whatever so they can communicate with one another. Dustin-PC= 192.168.1.7, VMnet1 = 192.168.1.8 and VMnet8 = 192.168.1.9. Remember that the last number can be anything between 2-254 as long as it's unique and isn't assigned to another device (I excluded 192.168.1.1 since it's typically assigned to the router and already used which is indicated below by your gateway address aka router ip address). Also remember that your subnet mask should be 255.255.255.0 for all machines and the DHCP, Default Gateway and DNS servers should also typically match Dustin-PC. You should be able to change the VMNet adapter settings in the VMWare software on Dustin-PC. Dustin-PC IPv4 Address. . . . . . . . . . . : 192.168.1.7(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : Tuesday, September 07, 2010 10:33:20 PM Lease Expires . . . . . . . . . . : Thursday, September 09, 2010 10:33:20 PM Default Gateway . . . . . . . . . : 192.168.1.1 DHCP Server . . . . . . . . . . . : 192.168.1.1 Ethernet adapter VMware Network Adapter VMnet1: Physical Address. . . . . . . . . : 00-50-56-C0-00-01 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv4 Address. . . . . . . . . . . : 192.168.116.1(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Ethernet adapter VMware Network Adapter VMnet8: Physical Address. . . . . . . . . : 00-50-56-C0-00-08 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv4 Address. . . . . . . . . . . : 192.168.142.1(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 |
It's been a long time since I have used VMware, but I remember there being the option under settings somewhere. With VirtualBox, when the VM is powered down there is a place under Settings > Network to change from NAT to bridging. I'll see if I can dig up some info on that for VMware and check at work. I thought the process to switch between them was easy.
|
| All times are GMT -4. The time now is 12:24 PM. |
Powered by vBulletin®, Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.