Link to home
Start Free TrialLog in
Avatar of talker2004
talker2004Flag for United States of America

asked on

Issues with x64 version of Virtual Server 2005 running on Windows Server 2008

I am having trouble connecting a vmrc client to a virtual server running on windows server 2008. I have turned off windows firewall and i have no trouble connecting from the client software installed onto the server 2008 box itself. It is all of the other machines on the network which are not able to connect to the virtual server. I am able to connect to the administrative website.

By the way i am connecting with the 32 bit version of the client software. The server is running the x64 version.

Any ideas?
Avatar of Halindar
Halindar
Flag of Netherlands image

Sounds like a routing problem to the Virtual server.

You can connect from the Host OS to the guest OS using the client installed on the Host OS.
This indicates the Host OS has routing information to reach the client OS.

What is the IP address space the guest OS is using, is it a different subnet from the Host OS?
If so check your network router and see if it has a routing entry for the guest OS address space with as a next hop gateway the Host OS IP.
That might solve your problem if it's a network routing based problem.
Avatar of talker2004

ASKER

My server is 192.168.1.100, 255.255.255.0. This address is statically defined inside of network connections with the approprate dns server to connect to my isp.

My router does have a dhcp server that starts dishing out addresses from 192.168.1.2 - 192.168.1.50. The router is automatically obtaining the dns servers from my isp. (comcast). The x64 Server 2008 box has not yet been promoted to a domain controller. When i try to connect with the vmrc client software from any of my workstations i get an error. I can post the exact error message here later this evening but is not the standard no connection.

After it fails to connect to the server it comes up something like this.
 "Connection to server lost"


btw the only machines using the dhcp server are virtual machines, game systems, pda's, cell phones. All of my physical workstations where i would be connected via vmrc are statically defined

Ok so your VMs are getting dynamic addresses assigned from the DHCP server in the 192.168.1.2 - 192.168.1.50 range?
Are the virtual interfaces for your VMs in NAT or Bridge mode? You can check in the settings screen of the VM.

Do an ipconfig /all inside the VM and on the host and please post the results here.
ok,  Since i have not yet forwarded port 3389 to my server i will not have access to it until tonight.  I will output the results from the vm and the host os and post it here.

Since it's release I have used the x86 version Virtual Server 2005 on Windows Server 2003 and have not once had any issues like this.
Here is the configuration. I am going to check some of the settings your were refferring to.


Host OS (Server 2008)

Windows IP Configuration

   Host Name . . . . . . . . . . . . : srv2k8
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connection
   Physical Address. . . . . . . . . : 00-13-72-D9-A3-16
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::b94e:3b48:f63c:408e%10(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.100(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.1
   DNS Servers . . . . . . . . . . . : 68.87.75.194
                                       68.87.64.146
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 8:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : isatap.{9F08A576-C09E-4CB1-8F3F-883110B9DA3E}
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 9:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 02-00-54-55-4E-01
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes


Guest OS (Server 2003)



Windows IP Configuration



   Host Name . . . . . . . . . . . . : srvvpc

   Primary Dns Suffix  . . . . . . . :

   Node Type . . . . . . . . . . . . : Unknown

   IP Routing Enabled. . . . . . . . : No

   WINS Proxy Enabled. . . . . . . . : No



Ethernet adapter Local Area Connection:



   Connection-specific DNS Suffix  . :

   Description . . . . . . . . . . . : Intel 21140-Based PCI Fast Ethernet Adapter (Generic)

   Physical Address. . . . . . . . . : 00-03-FF-D8-A3-16

   DHCP Enabled. . . . . . . . . . . : Yes

   Autoconfiguration Enabled . . . . : Yes

   IP Address. . . . . . . . . . . . : 192.168.1.4

   Subnet Mask . . . . . . . . . . . : 255.255.255.0

   Default Gateway . . . . . . . . . : 192.168.1.1

   DHCP Server . . . . . . . . . . . : 192.168.1.1

   DNS Servers . . . . . . . . . . . : 192.168.1.1

   Lease Obtained. . . . . . . . . . : Thursday, March 06, 2008 11:28:31 AM

   Lease Expires . . . . . . . . . . : Friday, March 07, 2008 11:28:31 AM

ASKER CERTIFIED SOLUTION
Avatar of Halindar
Halindar
Flag of Netherlands image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial