Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

VM Ware /Windows 2003 Server issue

Status
Not open for further replies.

GVN

MIS
Dec 2, 2005
238
US
For some reason I cannot map any network drives from my VM guest OS'es or add them to the domain. These are Windows 2003 Server Enterprise Edition guests. I've tried turning off Windows Firewall off on both the host server and the guest images, but no luck so far. Any ideas?... The host OS allowed me to add it to the domain and map network drives just fine... I'm stumped on this issue.

I've posted this same question on the VMTN Forum and no one can figure out the problem there either.


GVN
 
any specific error messages when mapping? how did you setup the vmware networking?

Roadki11
 
Initially I set it up as NAT, but then decided to change to a static IP address, so now it says 'bridged'. Is that the right setting for it to be at?

GVN
 
These are the VMware guest settings, sorry I didn't elaborate...

When I try to join the domain it tries for a couple of minutes, then I get an error message saying:

"The following error occurred attempting to join the domain "DomainName":
The network path was not found.
<< OK >>

Since you will probably want to see the IPCONFIG info for both the host OS and the guest OS, here it is:


HOST:

Windows IP Configuration

Host Name . . . . . . . . . . . . : SVR-HOST
Primary Dns Suffix . . . . . . . : example.com
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : example.com

Ethernet adapter VMware Network Adapter VMnet8:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet8
Physical Address. . . . . . . . . : 00-50-56-C0-00-08
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.25.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :

Ethernet adapter VMware Network Adapter VMnet1:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet1
Physical Address. . . . . . . . . : 00-50-56-C0-00-01
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.10.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Physical Address. . . . . . . . . : 02-BF-0A-00-00-10
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.0.0.16
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.0.0.254
DNS Servers . . . . . . . . . . . : 10.0.0.11
10.0.0.5

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet #2
Physical Address. . . . . . . . . : 02-BF-0A-00-00-11
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.0.0.17
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.0.0.254
DNS Servers . . . . . . . . . . . : 10.0.0.5
10.0.0.11
***************

GUEST:

Windows IP Configuration

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

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Accelerated AMD PCNet Adapter
Physical Address. . . . . . . . . : 00-0C-29-65-B8-1C
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.0.0.4
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.0.0.254
DNS Servers . . . . . . . . . . . : 10.0.0.11
10.0.0.5
Primary WINS Server . . . . . . . : 10.0.0.11
Secondary WINS Server . . . . . . : 10.0.0.5

 
i see you have 2 nics on the host and both are on the same network/subnet. are you teaming those nics or bridging them? what is idea behind 2 nics on the same network? bidging the guest os is how i usually do it. you can bind the guest to a specific host nic but it depends on how you have them setup, teaming or bridged or what not. make sure the guest os's have an A record in dns, also add a dns suffix on the guest os. when you try to join the domain try joing blahblah.com not blahblah.

RoadKi11
 
I was trying to team them... I was told by a speaker at a Virtualization conference that it is better to have multiple NIC in a VMware server because that is a typical bottleneck area...

I turned off NIC #2 now.
 
GSX right? You should be teaming at the host level not the VM level. The Virtual machine would only have one NIC. Make sure the TCP/IP properties for the VM are correct, IP - SM- Gateway - DNS IP - Domain Name. Just like any windows workstation, it need to query DNS for the DC's so that computer accounts can be created. Bridged Network is correct...
 
No, VMware Server, v. 1.0.1.

All that you mentioned is correct, just like any other "physical" server would be. I can ping to/from the guest just fine... just can't join the domain.
 
Hey, I went into 'Host' > 'Virtual Network Settings' > 'Host Virtual Network Mapping' and changed VMnet0 to the physical NIC in the machine instead of the "automatically chosen adapter" that was selected, and I got the ability to connect to a share on the guest OS from another machine on my network.

Now I need to figure out why the guest can't join the domain... Any ideas?

GVN
 
can you do an NSLOOKUP from a command prompt on the VM and does it resolve to your domains DNS servers?

example: nslookup yourdomain.com

From the DNS Tab under TCP/IP properties (on the VM) enter the domain name in the DNS Suffix text box.

For chits and giggle, when trying to add VM to domain use domainName\UserName for the user name.

Anything?
 
Yes, I can perform NSLOOKUPs and it resolves internal workstation names to their correct IP addresses.

I added the domain name in the DNS Suffix text box as you suggested, it said that it wanted to reboot so I let it do so.

I have been using the domainName\UserName format when I try to use credentials, as I always do. It's still failing to join the domain. I've tried 2 different Domain Admin account credentials, just to double-check. Same results both times...
 
What's the commandline syntax to add a machine to a domain? I'll try that...

GVN
 
when you do a nslookup on just the domain name, it does come back with the IP addresses of the DNS servers? Just curious, as you said it "resolves internal workstation names to their correct IP addresses." So I am confused a little. When you do:
nslookup YourdomainName.Com (without the hostname portion of the FQDN). you should see:
Server: DC1.YourDomain.COM
Address: 10.0.0.1

Name: YourDomain.org
Addresses: 10.0.0.1, 10.0.0.2 (depending on the number of DCs you have).
 
Since you are teaming your Physical NIC, could the issue be caused by the fact that each NIC has the Primary and Secondary DNS entries reversed? Just a stab from looking at you IP config.
 
I can't figure out the syntax of DSADD, even after doing a DSADD /? | more

If I want to add a computer named TEST1, what would be the syntax? 'DSADD computer TEST1' ???

 
You have to supply the path in AD (DistinguishedName)
Eg.
dsadd computer cn=computer1,cn=computers,dc=yourdomain,dc=com

This will add a computer named computer1 in the computers container in the domain.
 
I tried your syntax and it said that it could connect to the domain...
 
Not being able to connect ot the domain is the same symptom you are having when trying to add the computer via the OS. Please answer the following question:
when you do a nslookup on just the domain name, it does come back with the IP addresses of the DNS servers? Just curious, as you said it "resolves internal workstation names to their correct IP addresses." So I am confused a little. When you do:
nslookup YourdomainName.Com (without the hostname portion of the FQDN). you should see:
Server: DNS1.YourDomain.COM
Address: 10.0.0.1

Name: YourDomain.org
Addresses: 10.0.0.1, 10.0.0.2 (depending on the number of DCs you have).
 
Here's what I get:

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator>nslookup
Default Server: myDC1.myDomain.com
Address: 10.0.0.11

> myDomain.com
Server: myDC1.myDomain.com
Address: 10.0.0.11

Name: myDomain.com
Addresses: 10.0.0.14, 10.0.0.11, 10.0.0.5

>

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top