Creating a Virtual Domain

I have two virtual PCs (running Win2003 Enterprise SP1) hosted on my home
WinXP Pro SP2 (which is connected to my ISP). I am trying to create a domain
of the virtual PCs, but am encountering problems joining the second virtual
PC to the domain.

I converted the IP address of one Virtual PC to static, promoted it to a
domain controller, and installed DNS. I named the new domain
"mydomain.local".

Note also that I have assigned distinct names to each to each of the virtual
machines.

The second virtual PC has a dynamic IP address and belongs to WORKGROUP.

I am able to ping the virtual domain controller from the virtual client
machine. My exact network configuration is shown at the bottom of this
message.

When I attempt to join the client virtual PC to the domain (via Control
Panel => System =>
Computer Name => Change.), I get the standard login prompt (to which I enter
(E-Mail Removed)l and password). However, I then get the
following error:

--------------------------------------------------------------------------------------
The following error occurred when DNS was queried for the service location
(SRV) resource record used to locate a domain controller for domain
mydomain.local:

The error was: "DNS name does not exist."
(error code 0x0000232B RCODE_NAME_ERROR)

The query was for the SRV record for _ldap._tcp.dc._msdcs.mydomain.local

Common causes of this error include the following:

- The DNS SRV records required to locate a domain controller for the domain
are not registered in DNS. These records are registered with a DNS server
automatically when a domain controller is added to a domain. They are
updated by the domain controller at set intervals. This computer is
configured to use DNS servers with following IP addresses:

192.168.2.1

- One or more of the following zones do not include delegation to its child
zone:

mydomain.local
local
.. (the root zone)

--------------------------------------------------------------------------------------

This error is occurring because my virtual client is using the DNS of my ISP
and it is not able to "delegate" the join request to the "mydomain.local"
domain.

Alternatively, I have tried to configure my client virtual machine to use
the DNS of the virtual domain controller but that also leads to different
errors.

So my question is: How do I configure my setup so that the join request for
the domain from the virtaul client is successfully passed to the virtual
domain controller?

Thanks in advance for any help.

Regards,
Frank J. Reashore, MCSD.net, MCDBA

Vancouver, Canada

************************************************** ******

Windows XP Pro (Host PC + WORKGROUP)

Connection-specific DNS Suffix . : bc.hsia.telus.net
IP Address. . . . . . . . . . . . : 192.168.2.117 (dynamic)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1

Windows Server 2003 Enterprise (Virtual PC + Domain controller + DNS +
domain = mydomain.local)
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.2.2 (static)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1

Windows Server 2003 Enterprise (Virtual PC + Client + WORKGROUP)
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.2.120 (static)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1

Hi,

Check DNS settings on both virtual computers. IPconfig results that you
posted here did not show all the ipconfig settings. You should do

ipconifg /all

on all your computers and post here. The result will also show DNS and other
settings.

In general domain controller must also use Active Directory DNS (and _not_
e.g. ISP DNS server). So set the domain controller to point back to itself.
You could enter 192.168.2.2 under preferred DNS server or even better
127.0.0.1. Now restart NetLogon service on DC.
Now change preferred DNS settings on your virtual client that you would like
to join to domain "mydomain.local" to point to 192.168.2.2 (not -- here you
can't use 127.0.0.1 since there is no DNS installed on this server).

Now try to join your virtual client to mydomain.local domain.

Note: in general it is not best practice to use "mydomain.local" for
production Active Directory DNS name.

--
Mike
Microsoft MVP - Windows Security

"Frank J. Reashore" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>I have two virtual PCs (running Win2003 Enterprise SP1) hosted on my home
>WinXP Pro SP2 (which is connected to my ISP). I am trying to create a
>domain of the virtual PCs, but am encountering problems joining the second
>virtual PC to the domain.
>
> I converted the IP address of one Virtual PC to static, promoted it to a
> domain controller, and installed DNS. I named the new domain
> "mydomain.local".
>
> Note also that I have assigned distinct names to each to each of the
> virtual machines.
>
> The second virtual PC has a dynamic IP address and belongs to WORKGROUP.
>
> I am able to ping the virtual domain controller from the virtual client
> machine. My exact network configuration is shown at the bottom of this
> message.
>
> When I attempt to join the client virtual PC to the domain (via Control
> Panel => System =>
> Computer Name => Change.), I get the standard login prompt (to which I
> enter (E-Mail Removed)l and password). However, I then get the
> following error:
>
> --------------------------------------------------------------------------------------
> The following error occurred when DNS was queried for the service location
> (SRV) resource record used to locate a domain controller for domain
> mydomain.local:
>
> The error was: "DNS name does not exist."
> (error code 0x0000232B RCODE_NAME_ERROR)
>
> The query was for the SRV record for _ldap._tcp.dc._msdcs.mydomain.local
>
> Common causes of this error include the following:
>
> - The DNS SRV records required to locate a domain controller for the
> domain are not registered in DNS. These records are registered with a DNS
> server automatically when a domain controller is added to a domain. They
> are updated by the domain controller at set intervals. This computer is
> configured to use DNS servers with following IP addresses:
>
> 192.168.2.1
>
> - One or more of the following zones do not include delegation to its
> child zone:
>
> mydomain.local
> local
> . (the root zone)
>
> --------------------------------------------------------------------------------------
>
> This error is occurring because my virtual client is using the DNS of my
> ISP and it is not able to "delegate" the join request to the
> "mydomain.local" domain.
>
> Alternatively, I have tried to configure my client virtual machine to use
> the DNS of the virtual domain controller but that also leads to different
> errors.
>
> So my question is: How do I configure my setup so that the join request
> for the domain from the virtaul client is successfully passed to the
> virtual domain controller?
>
> Thanks in advance for any help.
>
> Regards,
> Frank J. Reashore, MCSD.net, MCDBA
>
> Vancouver, Canada
>
> ************************************************** ******
>
> Windows XP Pro (Host PC + WORKGROUP)
>
> Connection-specific DNS Suffix . : bc.hsia.telus.net
> IP Address. . . . . . . . . . . . : 192.168.2.117 (dynamic)
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.2.1
>
> Windows Server 2003 Enterprise (Virtual PC + Domain controller + DNS +
> domain = mydomain.local)
> Connection-specific DNS Suffix . :
> IP Address. . . . . . . . . . . . : 192.168.2.2 (static)
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.2.1
>
> Windows Server 2003 Enterprise (Virtual PC + Client + WORKGROUP)
> Connection-specific DNS Suffix . :
> IP Address. . . . . . . . . . . . : 192.168.2.120 (static)
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.2.1
>
>
>
>
>
>
>
>
>
>

Mike,

Thanks for your response.

Everything you said in your email made perfect sense. I have included
"ipconfig /all" results for the DC and client virtual PCs respectively at
the bottom of this message.

I believe you can verify (see below) that my network connection is exactly
as you had suggested.

The problem is that when I try to join the client to the domain I get a
"Windows cannot find the network path" error. Note, I logged in as
(E-Mail Removed)l

I ensured that my DC was rebooted.

Also, I am able to ping the DC from the client.

Cheers,
Frank


--------------------------------------------------------------------------------------------------------------

Windows IP Configuration

Host Name . . . . . . . . . . . . : vancouver
Primary Dns Suffix . . . . . . . : mydomain.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : mydomain.local

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel 21140-Based PCI Fast Ethernet
Adapter (Generic)
Physical Address. . . . . . . . . : 00-03-FF-1C-3E-38
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.2.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 127.0.0.1


Windows IP Configuration

Host Name . . . . . . . . . . . . : toronto
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Mixed
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-15-3E-38
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.2.120
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.2.2





"Miha Pihler [MVP]" <mihap-(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Hi,
>
> Check DNS settings on both virtual computers. IPconfig results that you
> posted here did not show all the ipconfig settings. You should do
>
> ipconifg /all
>
> on all your computers and post here. The result will also show DNS and
> other settings.
>
> In general domain controller must also use Active Directory DNS (and _not_
> e.g. ISP DNS server). So set the domain controller to point back to
> itself. You could enter 192.168.2.2 under preferred DNS server or even
> better 127.0.0.1. Now restart NetLogon service on DC.
> Now change preferred DNS settings on your virtual client that you would
> like to join to domain "mydomain.local" to point to 192.168.2.2 (not --
> here you can't use 127.0.0.1 since there is no DNS installed on this
> server).
>
> Now try to join your virtual client to mydomain.local domain.
>
> Note: in general it is not best practice to use "mydomain.local" for
> production Active Directory DNS name.
>
> --
> Mike
> Microsoft MVP - Windows Security
>
> "Frank J. Reashore" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>>I have two virtual PCs (running Win2003 Enterprise SP1) hosted on my home
>>WinXP Pro SP2 (which is connected to my ISP). I am trying to create a
>>domain of the virtual PCs, but am encountering problems joining the
>>second virtual PC to the domain.
>>
>> I converted the IP address of one Virtual PC to static, promoted it to a
>> domain controller, and installed DNS. I named the new domain
>> "mydomain.local".
>>
>> Note also that I have assigned distinct names to each to each of the
>> virtual machines.
>>
>> The second virtual PC has a dynamic IP address and belongs to WORKGROUP.
>>
>> I am able to ping the virtual domain controller from the virtual client
>> machine. My exact network configuration is shown at the bottom of this
>> message.
>>
>> When I attempt to join the client virtual PC to the domain (via Control
>> Panel => System =>
>> Computer Name => Change.), I get the standard login prompt (to which I
>> enter (E-Mail Removed)l and password). However, I then get the
>> following error:
>>
>> --------------------------------------------------------------------------------------
>> The following error occurred when DNS was queried for the service
>> location (SRV) resource record used to locate a domain controller for
>> domain mydomain.local:
>>
>> The error was: "DNS name does not exist."
>> (error code 0x0000232B RCODE_NAME_ERROR)
>>
>> The query was for the SRV record for _ldap._tcp.dc._msdcs.mydomain.local
>>
>> Common causes of this error include the following:
>>
>> - The DNS SRV records required to locate a domain controller for the
>> domain are not registered in DNS. These records are registered with a DNS
>> server automatically when a domain controller is added to a domain. They
>> are updated by the domain controller at set intervals. This computer is
>> configured to use DNS servers with following IP addresses:
>>
>> 192.168.2.1
>>
>> - One or more of the following zones do not include delegation to its
>> child zone:
>>
>> mydomain.local
>> local
>> . (the root zone)
>>
>> --------------------------------------------------------------------------------------
>>
>> This error is occurring because my virtual client is using the DNS of my
>> ISP and it is not able to "delegate" the join request to the
>> "mydomain.local" domain.
>>
>> Alternatively, I have tried to configure my client virtual machine to use
>> the DNS of the virtual domain controller but that also leads to different
>> errors.
>>
>> So my question is: How do I configure my setup so that the join request
>> for the domain from the virtaul client is successfully passed to the
>> virtual domain controller?
>>
>> Thanks in advance for any help.
>>
>> Regards,
>> Frank J. Reashore, MCSD.net, MCDBA
>>
>> Vancouver, Canada
>>
>> ************************************************** ******
>>
>> Windows XP Pro (Host PC + WORKGROUP)
>>
>> Connection-specific DNS Suffix . : bc.hsia.telus.net
>> IP Address. . . . . . . . . . . . : 192.168.2.117 (dynamic)
>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> Default Gateway . . . . . . . . . : 192.168.2.1
>>
>> Windows Server 2003 Enterprise (Virtual PC + Domain controller + DNS +
>> domain = mydomain.local)
>> Connection-specific DNS Suffix . :
>> IP Address. . . . . . . . . . . . : 192.168.2.2 (static)
>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> Default Gateway . . . . . . . . . : 192.168.2.1
>>
>> Windows Server 2003 Enterprise (Virtual PC + Client + WORKGROUP)
>> Connection-specific DNS Suffix . :
>> IP Address. . . . . . . . . . . . : 192.168.2.120 (static)
>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> Default Gateway . . . . . . . . . : 192.168.2.1
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
>

The machine wishing to join the domain needs to use the DC of the target
Domain as its DNS Server in the TCP/IP config. No DNS in TCP/IP settings =
no visible Domian = failed join.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/IS...cessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/t...dance/2004.asp
http://www.microsoft.com/isaserver/t...dance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
-----------------------------------------------------


"Frank J. Reashore" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I have two virtual PCs (running Win2003 Enterprise SP1) hosted on my home
> WinXP Pro SP2 (which is connected to my ISP). I am trying to create a
domain
> of the virtual PCs, but am encountering problems joining the second
virtual
> PC to the domain.
>
> I converted the IP address of one Virtual PC to static, promoted it to a
> domain controller, and installed DNS. I named the new domain
> "mydomain.local".
>
> Note also that I have assigned distinct names to each to each of the
virtual
> machines.
>
> The second virtual PC has a dynamic IP address and belongs to WORKGROUP.
>
> I am able to ping the virtual domain controller from the virtual client
> machine. My exact network configuration is shown at the bottom of this
> message.
>
> When I attempt to join the client virtual PC to the domain (via Control
> Panel => System =>
> Computer Name => Change.), I get the standard login prompt (to which I
enter
> (E-Mail Removed)l and password). However, I then get the
> following error:
>
> --------------------------------------------------------------------------
------------
> The following error occurred when DNS was queried for the service location
> (SRV) resource record used to locate a domain controller for domain
> mydomain.local:
>
> The error was: "DNS name does not exist."
> (error code 0x0000232B RCODE_NAME_ERROR)
>
> The query was for the SRV record for _ldap._tcp.dc._msdcs.mydomain.local
>
> Common causes of this error include the following:
>
> - The DNS SRV records required to locate a domain controller for the
domain
> are not registered in DNS. These records are registered with a DNS server
> automatically when a domain controller is added to a domain. They are
> updated by the domain controller at set intervals. This computer is
> configured to use DNS servers with following IP addresses:
>
> 192.168.2.1
>
> - One or more of the following zones do not include delegation to its
child
> zone:
>
> mydomain.local
> local
> . (the root zone)
>
> --------------------------------------------------------------------------
------------
>
> This error is occurring because my virtual client is using the DNS of my
ISP
> and it is not able to "delegate" the join request to the "mydomain.local"
> domain.
>
> Alternatively, I have tried to configure my client virtual machine to use
> the DNS of the virtual domain controller but that also leads to different
> errors.
>
> So my question is: How do I configure my setup so that the join request
for
> the domain from the virtaul client is successfully passed to the virtual
> domain controller?
>
> Thanks in advance for any help.
>
> Regards,
> Frank J. Reashore, MCSD.net, MCDBA
>
> Vancouver, Canada
>
> ************************************************** ******
>
> Windows XP Pro (Host PC + WORKGROUP)
>
> Connection-specific DNS Suffix . : bc.hsia.telus.net
> IP Address. . . . . . . . . . . . : 192.168.2.117 (dynamic)
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.2.1
>
> Windows Server 2003 Enterprise (Virtual PC + Domain controller + DNS +
> domain = mydomain.local)
> Connection-specific DNS Suffix . :
> IP Address. . . . . . . . . . . . : 192.168.2.2 (static)
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.2.1
>
> Windows Server 2003 Enterprise (Virtual PC + Client + WORKGROUP)
> Connection-specific DNS Suffix . :
> IP Address. . . . . . . . . . . . : 192.168.2.120 (static)
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.2.1
>
>
>
>
>
>
>
>
>
>

Phillip,

I believe that I am doing this. My "ipconfig /all" for the virtual DC
(vancouver) and virtual client (toronto) are listed at the end of this
message.

Note the client uses the a DNS of the DC, 192.168.2.2. The DC uses the local
DNS.

I have rebooted my DC. I am able to ping my DC from the client.

When I attempt to join the domain, "mydomain.local", I get the "Windows
cannot find the network path" error. Note that I am logging on as
(E-Mail Removed)l

I am puzzled. Maybe the mydomain.local is not aware of the WORKGROUP
computers.

Frank

--------------------------------------------------------------------------------------------------------------

Windows IP Configuration

Host Name . . . . . . . . . . . . : vancouver
Primary Dns Suffix . . . . . . . : mydomain.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : mydomain.local

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel 21140-Based PCI Fast Ethernet
Adapter (Generic)
Physical Address. . . . . . . . . : 00-03-FF-1C-3E-38
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.2.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 127.0.0.1




Windows IP Configuration

Host Name . . . . . . . . . . . . : toronto
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Mixed
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-15-3E-38
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.2.120
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.2.2






"Phillip Windell" <@.> wrote in message
news:%23Yh9$(E-Mail Removed)...
> The machine wishing to join the domain needs to use the DC of the target
> Domain as its DNS Server in the TCP/IP config. No DNS in TCP/IP settings
> =
> no visible Domian = failed join.
>
> --
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
> -----------------------------------------------------
> Understanding the ISA 2004 Access Rule Processing
> http://www.isaserver.org/articles/IS...cessRules.html
>
> Microsoft Internet Security & Acceleration Server: Guidance
> http://www.microsoft.com/isaserver/t...dance/2004.asp
> http://www.microsoft.com/isaserver/t...dance/2000.asp
>
> Microsoft Internet Security & Acceleration Server: Partners
> http://www.microsoft.com/isaserver/partners/default.asp
> -----------------------------------------------------
>
>
> "Frank J. Reashore" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> I have two virtual PCs (running Win2003 Enterprise SP1) hosted on my home
>> WinXP Pro SP2 (which is connected to my ISP). I am trying to create a
> domain
>> of the virtual PCs, but am encountering problems joining the second
> virtual
>> PC to the domain.
>>
>> I converted the IP address of one Virtual PC to static, promoted it to a
>> domain controller, and installed DNS. I named the new domain
>> "mydomain.local".
>>
>> Note also that I have assigned distinct names to each to each of the
> virtual
>> machines.
>>
>> The second virtual PC has a dynamic IP address and belongs to WORKGROUP.
>>
>> I am able to ping the virtual domain controller from the virtual client
>> machine. My exact network configuration is shown at the bottom of this
>> message.
>>
>> When I attempt to join the client virtual PC to the domain (via Control
>> Panel => System =>
>> Computer Name => Change.), I get the standard login prompt (to which I
> enter
>> (E-Mail Removed)l and password). However, I then get the
>> following error:
>>
>> --------------------------------------------------------------------------
> ------------
>> The following error occurred when DNS was queried for the service
>> location
>> (SRV) resource record used to locate a domain controller for domain
>> mydomain.local:
>>
>> The error was: "DNS name does not exist."
>> (error code 0x0000232B RCODE_NAME_ERROR)
>>
>> The query was for the SRV record for _ldap._tcp.dc._msdcs.mydomain.local
>>
>> Common causes of this error include the following:
>>
>> - The DNS SRV records required to locate a domain controller for the
> domain
>> are not registered in DNS. These records are registered with a DNS server
>> automatically when a domain controller is added to a domain. They are
>> updated by the domain controller at set intervals. This computer is
>> configured to use DNS servers with following IP addresses:
>>
>> 192.168.2.1
>>
>> - One or more of the following zones do not include delegation to its
> child
>> zone:
>>
>> mydomain.local
>> local
>> . (the root zone)
>>
>> --------------------------------------------------------------------------
> ------------
>>
>> This error is occurring because my virtual client is using the DNS of my
> ISP
>> and it is not able to "delegate" the join request to the "mydomain.local"
>> domain.
>>
>> Alternatively, I have tried to configure my client virtual machine to use
>> the DNS of the virtual domain controller but that also leads to different
>> errors.
>>
>> So my question is: How do I configure my setup so that the join request
> for
>> the domain from the virtaul client is successfully passed to the virtual
>> domain controller?
>>
>> Thanks in advance for any help.
>>
>> Regards,
>> Frank J. Reashore, MCSD.net, MCDBA
>>
>> Vancouver, Canada
>>
>> ************************************************** ******
>>
>> Windows XP Pro (Host PC + WORKGROUP)
>>
>> Connection-specific DNS Suffix . : bc.hsia.telus.net
>> IP Address. . . . . . . . . . . . : 192.168.2.117 (dynamic)
>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> Default Gateway . . . . . . . . . : 192.168.2.1
>>
>> Windows Server 2003 Enterprise (Virtual PC + Domain controller + DNS +
>> domain = mydomain.local)
>> Connection-specific DNS Suffix . :
>> IP Address. . . . . . . . . . . . : 192.168.2.2 (static)
>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> Default Gateway . . . . . . . . . : 192.168.2.1
>>
>> Windows Server 2003 Enterprise (Virtual PC + Client + WORKGROUP)
>> Connection-specific DNS Suffix . :
>> IP Address. . . . . . . . . . . . : 192.168.2.120 (static)
>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> Default Gateway . . . . . . . . . : 192.168.2.1
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
>

Hi,

few things to try.

What did you enter as name of domain to join? Did you enter NetBIOS name or
DNS name? Try DNS name e.g. mydomain.local

What happens if you try this on the client? Click Start -> Run and enter

\\vancouver\c$

What happens if you enter this:

\\192.168.2.2\c$

--
Mike
Microsoft MVP - Windows Security


"Frank J. Reashore" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Mike,
>
> Thanks for your response.
>
> Everything you said in your email made perfect sense. I have included
> "ipconfig /all" results for the DC and client virtual PCs respectively at
> the bottom of this message.
>
> I believe you can verify (see below) that my network connection is exactly
> as you had suggested.
>
> The problem is that when I try to join the client to the domain I get a
> "Windows cannot find the network path" error. Note, I logged in as
> (E-Mail Removed)l
>
> I ensured that my DC was rebooted.
>
> Also, I am able to ping the DC from the client.
>
> Cheers,
> Frank
>
>
> --------------------------------------------------------------------------------------------------------------
>
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : vancouver
> Primary Dns Suffix . . . . . . . : mydomain.local
> Node Type . . . . . . . . . . . . : Unknown
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : mydomain.local
>
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Intel 21140-Based PCI Fast Ethernet
> Adapter (Generic)
> Physical Address. . . . . . . . . : 00-03-FF-1C-3E-38
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.2.2
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.2.1
> DNS Servers . . . . . . . . . . . : 127.0.0.1
>
>
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : toronto
> Primary Dns Suffix . . . . . . . :
> Node Type . . . . . . . . . . . . : Mixed
> 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-15-3E-38
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.2.120
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.2.1
> DNS Servers . . . . . . . . . . . : 192.168.2.2
>
>
>
>
>
> "Miha Pihler [MVP]" <mihap-(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
>> Hi,
>>
>> Check DNS settings on both virtual computers. IPconfig results that you
>> posted here did not show all the ipconfig settings. You should do
>>
>> ipconifg /all
>>
>> on all your computers and post here. The result will also show DNS and
>> other settings.
>>
>> In general domain controller must also use Active Directory DNS (and
>> _not_ e.g. ISP DNS server). So set the domain controller to point back to
>> itself. You could enter 192.168.2.2 under preferred DNS server or even
>> better 127.0.0.1. Now restart NetLogon service on DC.
>> Now change preferred DNS settings on your virtual client that you would
>> like to join to domain "mydomain.local" to point to 192.168.2.2 (not --
>> here you can't use 127.0.0.1 since there is no DNS installed on this
>> server).
>>
>> Now try to join your virtual client to mydomain.local domain.
>>
>> Note: in general it is not best practice to use "mydomain.local" for
>> production Active Directory DNS name.
>>
>> --
>> Mike
>> Microsoft MVP - Windows Security
>>
>> "Frank J. Reashore" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>>I have two virtual PCs (running Win2003 Enterprise SP1) hosted on my home
>>>WinXP Pro SP2 (which is connected to my ISP). I am trying to create a
>>>domain of the virtual PCs, but am encountering problems joining the
>>>second virtual PC to the domain.
>>>
>>> I converted the IP address of one Virtual PC to static, promoted it to a
>>> domain controller, and installed DNS. I named the new domain
>>> "mydomain.local".
>>>
>>> Note also that I have assigned distinct names to each to each of the
>>> virtual machines.
>>>
>>> The second virtual PC has a dynamic IP address and belongs to WORKGROUP.
>>>
>>> I am able to ping the virtual domain controller from the virtual client
>>> machine. My exact network configuration is shown at the bottom of this
>>> message.
>>>
>>> When I attempt to join the client virtual PC to the domain (via Control
>>> Panel => System =>
>>> Computer Name => Change.), I get the standard login prompt (to which I
>>> enter (E-Mail Removed)l and password). However, I then get
>>> the following error:
>>>
>>> --------------------------------------------------------------------------------------
>>> The following error occurred when DNS was queried for the service
>>> location (SRV) resource record used to locate a domain controller for
>>> domain mydomain.local:
>>>
>>> The error was: "DNS name does not exist."
>>> (error code 0x0000232B RCODE_NAME_ERROR)
>>>
>>> The query was for the SRV record for _ldap._tcp.dc._msdcs.mydomain.local
>>>
>>> Common causes of this error include the following:
>>>
>>> - The DNS SRV records required to locate a domain controller for the
>>> domain are not registered in DNS. These records are registered with a
>>> DNS server automatically when a domain controller is added to a domain.
>>> They are updated by the domain controller at set intervals. This
>>> computer is configured to use DNS servers with following IP addresses:
>>>
>>> 192.168.2.1
>>>
>>> - One or more of the following zones do not include delegation to its
>>> child zone:
>>>
>>> mydomain.local
>>> local
>>> . (the root zone)
>>>
>>> --------------------------------------------------------------------------------------
>>>
>>> This error is occurring because my virtual client is using the DNS of my
>>> ISP and it is not able to "delegate" the join request to the
>>> "mydomain.local" domain.
>>>
>>> Alternatively, I have tried to configure my client virtual machine to
>>> use the DNS of the virtual domain controller but that also leads to
>>> different errors.
>>>
>>> So my question is: How do I configure my setup so that the join request
>>> for the domain from the virtaul client is successfully passed to the
>>> virtual domain controller?
>>>
>>> Thanks in advance for any help.
>>>
>>> Regards,
>>> Frank J. Reashore, MCSD.net, MCDBA
>>>
>>> Vancouver, Canada
>>>
>>> ************************************************** ******
>>>
>>> Windows XP Pro (Host PC + WORKGROUP)
>>>
>>> Connection-specific DNS Suffix . : bc.hsia.telus.net
>>> IP Address. . . . . . . . . . . . : 192.168.2.117 (dynamic)
>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>> Default Gateway . . . . . . . . . : 192.168.2.1
>>>
>>> Windows Server 2003 Enterprise (Virtual PC + Domain controller + DNS +
>>> domain = mydomain.local)
>>> Connection-specific DNS Suffix . :
>>> IP Address. . . . . . . . . . . . : 192.168.2.2 (static)
>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>> Default Gateway . . . . . . . . . : 192.168.2.1
>>>
>>> Windows Server 2003 Enterprise (Virtual PC + Client + WORKGROUP)
>>> Connection-specific DNS Suffix . :
>>> IP Address. . . . . . . . . . . . : 192.168.2.120 (static)
>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>> Default Gateway . . . . . . . . . : 192.168.2.1
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>
>

Miha,

Thanks for your response.

I did use the DNS form of the domain name, mydomain.local, when I tried to
join the domain.

I also logged in to the security dialog using (E-Mail Removed)l.

Both tests to access $C failed with the message "No network provider
accepted the given network path".

Interesting, however I can still ping 192.168.2.2 successfully.

Regards,
Frank


"Miha Pihler [MVP]" <mihap-(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Hi,
>
> few things to try.
>
> What did you enter as name of domain to join? Did you enter NetBIOS name
> or DNS name? Try DNS name e.g. mydomain.local
>
> What happens if you try this on the client? Click Start -> Run and enter
>
> \\vancouver\c$
>
> What happens if you enter this:
>
> \\192.168.2.2\c$
>
> --
> Mike
> Microsoft MVP - Windows Security
>
>
> "Frank J. Reashore" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Mike,
>>
>> Thanks for your response.
>>
>> Everything you said in your email made perfect sense. I have included
>> "ipconfig /all" results for the DC and client virtual PCs respectively at
>> the bottom of this message.
>>
>> I believe you can verify (see below) that my network connection is
>> exactly as you had suggested.
>>
>> The problem is that when I try to join the client to the domain I get a
>> "Windows cannot find the network path" error. Note, I logged in as
>> (E-Mail Removed)l
>>
>> I ensured that my DC was rebooted.
>>
>> Also, I am able to ping the DC from the client.
>>
>> Cheers,
>> Frank
>>
>>
>> --------------------------------------------------------------------------------------------------------------
>>
>> Windows IP Configuration
>>
>> Host Name . . . . . . . . . . . . : vancouver
>> Primary Dns Suffix . . . . . . . : mydomain.local
>> Node Type . . . . . . . . . . . . : Unknown
>> IP Routing Enabled. . . . . . . . : No
>> WINS Proxy Enabled. . . . . . . . : No
>> DNS Suffix Search List. . . . . . : mydomain.local
>>
>> Ethernet adapter Local Area Connection:
>>
>> Connection-specific DNS Suffix . :
>> Description . . . . . . . . . . . : Intel 21140-Based PCI Fast Ethernet
>> Adapter (Generic)
>> Physical Address. . . . . . . . . : 00-03-FF-1C-3E-38
>> DHCP Enabled. . . . . . . . . . . : No
>> IP Address. . . . . . . . . . . . : 192.168.2.2
>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> Default Gateway . . . . . . . . . : 192.168.2.1
>> DNS Servers . . . . . . . . . . . : 127.0.0.1
>>
>>
>> Windows IP Configuration
>>
>> Host Name . . . . . . . . . . . . : toronto
>> Primary Dns Suffix . . . . . . . :
>> Node Type . . . . . . . . . . . . : Mixed
>> 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-15-3E-38
>> DHCP Enabled. . . . . . . . . . . : No
>> IP Address. . . . . . . . . . . . : 192.168.2.120
>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> Default Gateway . . . . . . . . . : 192.168.2.1
>> DNS Servers . . . . . . . . . . . : 192.168.2.2
>>
>>
>>
>>
>>
>> "Miha Pihler [MVP]" <mihap-(E-Mail Removed)> wrote in message
>> news:%(E-Mail Removed)...
>>> Hi,
>>>
>>> Check DNS settings on both virtual computers. IPconfig results that you
>>> posted here did not show all the ipconfig settings. You should do
>>>
>>> ipconifg /all
>>>
>>> on all your computers and post here. The result will also show DNS and
>>> other settings.
>>>
>>> In general domain controller must also use Active Directory DNS (and
>>> _not_ e.g. ISP DNS server). So set the domain controller to point back
>>> to itself. You could enter 192.168.2.2 under preferred DNS server or
>>> even better 127.0.0.1. Now restart NetLogon service on DC.
>>> Now change preferred DNS settings on your virtual client that you would
>>> like to join to domain "mydomain.local" to point to 192.168.2.2 (not --
>>> here you can't use 127.0.0.1 since there is no DNS installed on this
>>> server).
>>>
>>> Now try to join your virtual client to mydomain.local domain.
>>>
>>> Note: in general it is not best practice to use "mydomain.local" for
>>> production Active Directory DNS name.
>>>
>>> --
>>> Mike
>>> Microsoft MVP - Windows Security
>>>
>>> "Frank J. Reashore" <(E-Mail Removed)> wrote in message
>>> news:(E-Mail Removed)...
>>>>I have two virtual PCs (running Win2003 Enterprise SP1) hosted on my
>>>>home WinXP Pro SP2 (which is connected to my ISP). I am trying to create
>>>>a domain of the virtual PCs, but am encountering problems joining the
>>>>second virtual PC to the domain.
>>>>
>>>> I converted the IP address of one Virtual PC to static, promoted it to
>>>> a domain controller, and installed DNS. I named the new domain
>>>> "mydomain.local".
>>>>
>>>> Note also that I have assigned distinct names to each to each of the
>>>> virtual machines.
>>>>
>>>> The second virtual PC has a dynamic IP address and belongs to
>>>> WORKGROUP.
>>>>
>>>> I am able to ping the virtual domain controller from the virtual client
>>>> machine. My exact network configuration is shown at the bottom of this
>>>> message.
>>>>
>>>> When I attempt to join the client virtual PC to the domain (via Control
>>>> Panel => System =>
>>>> Computer Name => Change.), I get the standard login prompt (to which I
>>>> enter (E-Mail Removed)l and password). However, I then get
>>>> the following error:
>>>>
>>>> --------------------------------------------------------------------------------------
>>>> The following error occurred when DNS was queried for the service
>>>> location (SRV) resource record used to locate a domain controller for
>>>> domain mydomain.local:
>>>>
>>>> The error was: "DNS name does not exist."
>>>> (error code 0x0000232B RCODE_NAME_ERROR)
>>>>
>>>> The query was for the SRV record for
>>>> _ldap._tcp.dc._msdcs.mydomain.local
>>>>
>>>> Common causes of this error include the following:
>>>>
>>>> - The DNS SRV records required to locate a domain controller for the
>>>> domain are not registered in DNS. These records are registered with a
>>>> DNS server automatically when a domain controller is added to a domain.
>>>> They are updated by the domain controller at set intervals. This
>>>> computer is configured to use DNS servers with following IP addresses:
>>>>
>>>> 192.168.2.1
>>>>
>>>> - One or more of the following zones do not include delegation to its
>>>> child zone:
>>>>
>>>> mydomain.local
>>>> local
>>>> . (the root zone)
>>>>
>>>> --------------------------------------------------------------------------------------
>>>>
>>>> This error is occurring because my virtual client is using the DNS of
>>>> my ISP and it is not able to "delegate" the join request to the
>>>> "mydomain.local" domain.
>>>>
>>>> Alternatively, I have tried to configure my client virtual machine to
>>>> use the DNS of the virtual domain controller but that also leads to
>>>> different errors.
>>>>
>>>> So my question is: How do I configure my setup so that the join request
>>>> for the domain from the virtaul client is successfully passed to the
>>>> virtual domain controller?
>>>>
>>>> Thanks in advance for any help.
>>>>
>>>> Regards,
>>>> Frank J. Reashore, MCSD.net, MCDBA
>>>>
>>>> Vancouver, Canada
>>>>
>>>> ************************************************** ******
>>>>
>>>> Windows XP Pro (Host PC + WORKGROUP)
>>>>
>>>> Connection-specific DNS Suffix . : bc.hsia.telus.net
>>>> IP Address. . . . . . . . . . . . : 192.168.2.117 (dynamic)
>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>>> Default Gateway . . . . . . . . . : 192.168.2.1
>>>>
>>>> Windows Server 2003 Enterprise (Virtual PC + Domain controller + DNS +
>>>> domain = mydomain.local)
>>>> Connection-specific DNS Suffix . :
>>>> IP Address. . . . . . . . . . . . : 192.168.2.2 (static)
>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>>> Default Gateway . . . . . . . . . : 192.168.2.1
>>>>
>>>> Windows Server 2003 Enterprise (Virtual PC + Client + WORKGROUP)
>>>> Connection-specific DNS Suffix . :
>>>> IP Address. . . . . . . . . . . . : 192.168.2.120 (static)
>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>>> Default Gateway . . . . . . . . . : 192.168.2.1
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

Hi,

Which service pack do you have on your XP client?

After you ping the server from the client, can you run

arp -a

on the client and post back the result for 192.168.2.2

--
Mike
Microsoft MVP - Windows Security

"Frank J. Reashore" <(E-Mail Removed)> wrote in message
news:e%(E-Mail Removed)...
> Miha,
>
> Thanks for your response.
>
> I did use the DNS form of the domain name, mydomain.local, when I tried to
> join the domain.
>
> I also logged in to the security dialog using
> (E-Mail Removed)l.
>
> Both tests to access $C failed with the message "No network provider
> accepted the given network path".
>
> Interesting, however I can still ping 192.168.2.2 successfully.
>
> Regards,
> Frank
>
>
> "Miha Pihler [MVP]" <mihap-(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
>> Hi,
>>
>> few things to try.
>>
>> What did you enter as name of domain to join? Did you enter NetBIOS name
>> or DNS name? Try DNS name e.g. mydomain.local
>>
>> What happens if you try this on the client? Click Start -> Run and enter
>>
>> \\vancouver\c$
>>
>> What happens if you enter this:
>>
>> \\192.168.2.2\c$
>>
>> --
>> Mike
>> Microsoft MVP - Windows Security
>>
>>
>> "Frank J. Reashore" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>> Mike,
>>>
>>> Thanks for your response.
>>>
>>> Everything you said in your email made perfect sense. I have included
>>> "ipconfig /all" results for the DC and client virtual PCs respectively
>>> at the bottom of this message.
>>>
>>> I believe you can verify (see below) that my network connection is
>>> exactly as you had suggested.
>>>
>>> The problem is that when I try to join the client to the domain I get a
>>> "Windows cannot find the network path" error. Note, I logged in as
>>> (E-Mail Removed)l
>>>
>>> I ensured that my DC was rebooted.
>>>
>>> Also, I am able to ping the DC from the client.
>>>
>>> Cheers,
>>> Frank
>>>
>>>
>>> --------------------------------------------------------------------------------------------------------------
>>>
>>> Windows IP Configuration
>>>
>>> Host Name . . . . . . . . . . . . : vancouver
>>> Primary Dns Suffix . . . . . . . : mydomain.local
>>> Node Type . . . . . . . . . . . . : Unknown
>>> IP Routing Enabled. . . . . . . . : No
>>> WINS Proxy Enabled. . . . . . . . : No
>>> DNS Suffix Search List. . . . . . : mydomain.local
>>>
>>> Ethernet adapter Local Area Connection:
>>>
>>> Connection-specific DNS Suffix . :
>>> Description . . . . . . . . . . . : Intel 21140-Based PCI Fast
>>> Ethernet Adapter (Generic)
>>> Physical Address. . . . . . . . . : 00-03-FF-1C-3E-38
>>> DHCP Enabled. . . . . . . . . . . : No
>>> IP Address. . . . . . . . . . . . : 192.168.2.2
>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>> Default Gateway . . . . . . . . . : 192.168.2.1
>>> DNS Servers . . . . . . . . . . . : 127.0.0.1
>>>
>>>
>>> Windows IP Configuration
>>>
>>> Host Name . . . . . . . . . . . . : toronto
>>> Primary Dns Suffix . . . . . . . :
>>> Node Type . . . . . . . . . . . . : Mixed
>>> 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-15-3E-38
>>> DHCP Enabled. . . . . . . . . . . : No
>>> IP Address. . . . . . . . . . . . : 192.168.2.120
>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>> Default Gateway . . . . . . . . . : 192.168.2.1
>>> DNS Servers . . . . . . . . . . . : 192.168.2.2
>>>
>>>
>>>
>>>
>>>
>>> "Miha Pihler [MVP]" <mihap-(E-Mail Removed)> wrote in message
>>> news:%(E-Mail Removed)...
>>>> Hi,
>>>>
>>>> Check DNS settings on both virtual computers. IPconfig results that you
>>>> posted here did not show all the ipconfig settings. You should do
>>>>
>>>> ipconifg /all
>>>>
>>>> on all your computers and post here. The result will also show DNS and
>>>> other settings.
>>>>
>>>> In general domain controller must also use Active Directory DNS (and
>>>> _not_ e.g. ISP DNS server). So set the domain controller to point back
>>>> to itself. You could enter 192.168.2.2 under preferred DNS server or
>>>> even better 127.0.0.1. Now restart NetLogon service on DC.
>>>> Now change preferred DNS settings on your virtual client that you would
>>>> like to join to domain "mydomain.local" to point to 192.168.2.2 (not --
>>>> here you can't use 127.0.0.1 since there is no DNS installed on this
>>>> server).
>>>>
>>>> Now try to join your virtual client to mydomain.local domain.
>>>>
>>>> Note: in general it is not best practice to use "mydomain.local" for
>>>> production Active Directory DNS name.
>>>>
>>>> --
>>>> Mike
>>>> Microsoft MVP - Windows Security
>>>>
>>>> "Frank J. Reashore" <(E-Mail Removed)> wrote in message
>>>> news:(E-Mail Removed)...
>>>>>I have two virtual PCs (running Win2003 Enterprise SP1) hosted on my
>>>>>home WinXP Pro SP2 (which is connected to my ISP). I am trying to
>>>>>create a domain of the virtual PCs, but am encountering problems
>>>>>joining the second virtual PC to the domain.
>>>>>
>>>>> I converted the IP address of one Virtual PC to static, promoted it to
>>>>> a domain controller, and installed DNS. I named the new domain
>>>>> "mydomain.local".
>>>>>
>>>>> Note also that I have assigned distinct names to each to each of the
>>>>> virtual machines.
>>>>>
>>>>> The second virtual PC has a dynamic IP address and belongs to
>>>>> WORKGROUP.
>>>>>
>>>>> I am able to ping the virtual domain controller from the virtual
>>>>> client machine. My exact network configuration is shown at the bottom
>>>>> of this message.
>>>>>
>>>>> When I attempt to join the client virtual PC to the domain (via
>>>>> Control Panel => System =>
>>>>> Computer Name => Change.), I get the standard login prompt (to which I
>>>>> enter (E-Mail Removed)l and password). However, I then get
>>>>> the following error:
>>>>>
>>>>> --------------------------------------------------------------------------------------
>>>>> The following error occurred when DNS was queried for the service
>>>>> location (SRV) resource record used to locate a domain controller for
>>>>> domain mydomain.local:
>>>>>
>>>>> The error was: "DNS name does not exist."
>>>>> (error code 0x0000232B RCODE_NAME_ERROR)
>>>>>
>>>>> The query was for the SRV record for
>>>>> _ldap._tcp.dc._msdcs.mydomain.local
>>>>>
>>>>> Common causes of this error include the following:
>>>>>
>>>>> - The DNS SRV records required to locate a domain controller for the
>>>>> domain are not registered in DNS. These records are registered with a
>>>>> DNS server automatically when a domain controller is added to a
>>>>> domain. They are updated by the domain controller at set intervals.
>>>>> This computer is configured to use DNS servers with following IP
>>>>> addresses:
>>>>>
>>>>> 192.168.2.1
>>>>>
>>>>> - One or more of the following zones do not include delegation to its
>>>>> child zone:
>>>>>
>>>>> mydomain.local
>>>>> local
>>>>> . (the root zone)
>>>>>
>>>>> --------------------------------------------------------------------------------------
>>>>>
>>>>> This error is occurring because my virtual client is using the DNS of
>>>>> my ISP and it is not able to "delegate" the join request to the
>>>>> "mydomain.local" domain.
>>>>>
>>>>> Alternatively, I have tried to configure my client virtual machine to
>>>>> use the DNS of the virtual domain controller but that also leads to
>>>>> different errors.
>>>>>
>>>>> So my question is: How do I configure my setup so that the join
>>>>> request for the domain from the virtaul client is successfully passed
>>>>> to the virtual domain controller?
>>>>>
>>>>> Thanks in advance for any help.
>>>>>
>>>>> Regards,
>>>>> Frank J. Reashore, MCSD.net, MCDBA
>>>>>
>>>>> Vancouver, Canada
>>>>>
>>>>> ************************************************** ******
>>>>>
>>>>> Windows XP Pro (Host PC + WORKGROUP)
>>>>>
>>>>> Connection-specific DNS Suffix . : bc.hsia.telus.net
>>>>> IP Address. . . . . . . . . . . . : 192.168.2.117 (dynamic)
>>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>>>> Default Gateway . . . . . . . . . : 192.168.2.1
>>>>>
>>>>> Windows Server 2003 Enterprise (Virtual PC + Domain controller + DNS +
>>>>> domain = mydomain.local)
>>>>> Connection-specific DNS Suffix . :
>>>>> IP Address. . . . . . . . . . . . : 192.168.2.2 (static)
>>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>>>> Default Gateway . . . . . . . . . : 192.168.2.1
>>>>>
>>>>> Windows Server 2003 Enterprise (Virtual PC + Client + WORKGROUP)
>>>>> Connection-specific DNS Suffix . :
>>>>> IP Address. . . . . . . . . . . . : 192.168.2.120 (static)
>>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>>>> Default Gateway . . . . . . . . . : 192.168.2.1
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

Can you also check if this will help...

Cannot access shares or printers across the LAN from Windows XP
http://support.microsoft.com/kb/841570

--
Mike
Microsoft MVP - Windows Security

"Frank J. Reashore" <(E-Mail Removed)> wrote in message
news:e%(E-Mail Removed)...
> Miha,
>
> Thanks for your response.
>
> I did use the DNS form of the domain name, mydomain.local, when I tried to
> join the domain.
>
> I also logged in to the security dialog using
> (E-Mail Removed)l.
>
> Both tests to access $C failed with the message "No network provider
> accepted the given network path".
>
> Interesting, however I can still ping 192.168.2.2 successfully.
>
> Regards,
> Frank
>
>
> "Miha Pihler [MVP]" <mihap-(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
>> Hi,
>>
>> few things to try.
>>
>> What did you enter as name of domain to join? Did you enter NetBIOS name
>> or DNS name? Try DNS name e.g. mydomain.local
>>
>> What happens if you try this on the client? Click Start -> Run and enter
>>
>> \\vancouver\c$
>>
>> What happens if you enter this:
>>
>> \\192.168.2.2\c$
>>
>> --
>> Mike
>> Microsoft MVP - Windows Security
>>
>>
>> "Frank J. Reashore" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>> Mike,
>>>
>>> Thanks for your response.
>>>
>>> Everything you said in your email made perfect sense. I have included
>>> "ipconfig /all" results for the DC and client virtual PCs respectively
>>> at the bottom of this message.
>>>
>>> I believe you can verify (see below) that my network connection is
>>> exactly as you had suggested.
>>>
>>> The problem is that when I try to join the client to the domain I get a
>>> "Windows cannot find the network path" error. Note, I logged in as
>>> (E-Mail Removed)l
>>>
>>> I ensured that my DC was rebooted.
>>>
>>> Also, I am able to ping the DC from the client.
>>>
>>> Cheers,
>>> Frank
>>>
>>>
>>> --------------------------------------------------------------------------------------------------------------
>>>
>>> Windows IP Configuration
>>>
>>> Host Name . . . . . . . . . . . . : vancouver
>>> Primary Dns Suffix . . . . . . . : mydomain.local
>>> Node Type . . . . . . . . . . . . : Unknown
>>> IP Routing Enabled. . . . . . . . : No
>>> WINS Proxy Enabled. . . . . . . . : No
>>> DNS Suffix Search List. . . . . . : mydomain.local
>>>
>>> Ethernet adapter Local Area Connection:
>>>
>>> Connection-specific DNS Suffix . :
>>> Description . . . . . . . . . . . : Intel 21140-Based PCI Fast
>>> Ethernet Adapter (Generic)
>>> Physical Address. . . . . . . . . : 00-03-FF-1C-3E-38
>>> DHCP Enabled. . . . . . . . . . . : No
>>> IP Address. . . . . . . . . . . . : 192.168.2.2
>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>> Default Gateway . . . . . . . . . : 192.168.2.1
>>> DNS Servers . . . . . . . . . . . : 127.0.0.1
>>>
>>>
>>> Windows IP Configuration
>>>
>>> Host Name . . . . . . . . . . . . : toronto
>>> Primary Dns Suffix . . . . . . . :
>>> Node Type . . . . . . . . . . . . : Mixed
>>> 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-15-3E-38
>>> DHCP Enabled. . . . . . . . . . . : No
>>> IP Address. . . . . . . . . . . . : 192.168.2.120
>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>> Default Gateway . . . . . . . . . : 192.168.2.1
>>> DNS Servers . . . . . . . . . . . : 192.168.2.2
>>>
>>>
>>>
>>>
>>>
>>> "Miha Pihler [MVP]" <mihap-(E-Mail Removed)> wrote in message
>>> news:%(E-Mail Removed)...
>>>> Hi,
>>>>
>>>> Check DNS settings on both virtual computers. IPconfig results that you
>>>> posted here did not show all the ipconfig settings. You should do
>>>>
>>>> ipconifg /all
>>>>
>>>> on all your computers and post here. The result will also show DNS and
>>>> other settings.
>>>>
>>>> In general domain controller must also use Active Directory DNS (and
>>>> _not_ e.g. ISP DNS server). So set the domain controller to point back
>>>> to itself. You could enter 192.168.2.2 under preferred DNS server or
>>>> even better 127.0.0.1. Now restart NetLogon service on DC.
>>>> Now change preferred DNS settings on your virtual client that you would
>>>> like to join to domain "mydomain.local" to point to 192.168.2.2 (not --
>>>> here you can't use 127.0.0.1 since there is no DNS installed on this
>>>> server).
>>>>
>>>> Now try to join your virtual client to mydomain.local domain.
>>>>
>>>> Note: in general it is not best practice to use "mydomain.local" for
>>>> production Active Directory DNS name.
>>>>
>>>> --
>>>> Mike
>>>> Microsoft MVP - Windows Security
>>>>
>>>> "Frank J. Reashore" <(E-Mail Removed)> wrote in message
>>>> news:(E-Mail Removed)...
>>>>>I have two virtual PCs (running Win2003 Enterprise SP1) hosted on my
>>>>>home WinXP Pro SP2 (which is connected to my ISP). I am trying to
>>>>>create a domain of the virtual PCs, but am encountering problems
>>>>>joining the second virtual PC to the domain.
>>>>>
>>>>> I converted the IP address of one Virtual PC to static, promoted it to
>>>>> a domain controller, and installed DNS. I named the new domain
>>>>> "mydomain.local".
>>>>>
>>>>> Note also that I have assigned distinct names to each to each of the
>>>>> virtual machines.
>>>>>
>>>>> The second virtual PC has a dynamic IP address and belongs to
>>>>> WORKGROUP.
>>>>>
>>>>> I am able to ping the virtual domain controller from the virtual
>>>>> client machine. My exact network configuration is shown at the bottom
>>>>> of this message.
>>>>>
>>>>> When I attempt to join the client virtual PC to the domain (via
>>>>> Control Panel => System =>
>>>>> Computer Name => Change.), I get the standard login prompt (to which I
>>>>> enter (E-Mail Removed)l and password). However, I then get
>>>>> the following error:
>>>>>
>>>>> --------------------------------------------------------------------------------------
>>>>> The following error occurred when DNS was queried for the service
>>>>> location (SRV) resource record used to locate a domain controller for
>>>>> domain mydomain.local:
>>>>>
>>>>> The error was: "DNS name does not exist."
>>>>> (error code 0x0000232B RCODE_NAME_ERROR)
>>>>>
>>>>> The query was for the SRV record for
>>>>> _ldap._tcp.dc._msdcs.mydomain.local
>>>>>
>>>>> Common causes of this error include the following:
>>>>>
>>>>> - The DNS SRV records required to locate a domain controller for the
>>>>> domain are not registered in DNS. These records are registered with a
>>>>> DNS server automatically when a domain controller is added to a
>>>>> domain. They are updated by the domain controller at set intervals.
>>>>> This computer is configured to use DNS servers with following IP
>>>>> addresses:
>>>>>
>>>>> 192.168.2.1
>>>>>
>>>>> - One or more of the following zones do not include delegation to its
>>>>> child zone:
>>>>>
>>>>> mydomain.local
>>>>> local
>>>>> . (the root zone)
>>>>>
>>>>> --------------------------------------------------------------------------------------
>>>>>
>>>>> This error is occurring because my virtual client is using the DNS of
>>>>> my ISP and it is not able to "delegate" the join request to the
>>>>> "mydomain.local" domain.
>>>>>
>>>>> Alternatively, I have tried to configure my client virtual machine to
>>>>> use the DNS of the virtual domain controller but that also leads to
>>>>> different errors.
>>>>>
>>>>> So my question is: How do I configure my setup so that the join
>>>>> request for the domain from the virtaul client is successfully passed
>>>>> to the virtual domain controller?
>>>>>
>>>>> Thanks in advance for any help.
>>>>>
>>>>> Regards,
>>>>> Frank J. Reashore, MCSD.net, MCDBA
>>>>>
>>>>> Vancouver, Canada
>>>>>
>>>>> ************************************************** ******
>>>>>
>>>>> Windows XP Pro (Host PC + WORKGROUP)
>>>>>
>>>>> Connection-specific DNS Suffix . : bc.hsia.telus.net
>>>>> IP Address. . . . . . . . . . . . : 192.168.2.117 (dynamic)
>>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>>>> Default Gateway . . . . . . . . . : 192.168.2.1
>>>>>
>>>>> Windows Server 2003 Enterprise (Virtual PC + Domain controller + DNS +
>>>>> domain = mydomain.local)
>>>>> Connection-specific DNS Suffix . :
>>>>> IP Address. . . . . . . . . . . . : 192.168.2.2 (static)
>>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>>>> Default Gateway . . . . . . . . . : 192.168.2.1
>>>>>
>>>>> Windows Server 2003 Enterprise (Virtual PC + Client + WORKGROUP)
>>>>> Connection-specific DNS Suffix . :
>>>>> IP Address. . . . . . . . . . . . : 192.168.2.120 (static)
>>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>>>> Default Gateway . . . . . . . . . : 192.168.2.1
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

Question?? Is the DC running any web services? web server(apache,
bulletproof) etc... if it is then your DNS is probably having you go
out to the internet and back in to your LAN to access anything. You
would need to make an entry in the hosts file on the client, pointing
it to the internal IP of the server for the hostname.

Easy way to tell is to ping the server name from a client?? does it
resolve to an internal Ip or external??

If it resolves to the external IP then this is what you need. - if it
resolved to the internal then disregard what I have said.

c:\windows\system32\driver\etc\hosts

add line

server internal Ip servername

this will allow your local client to access the server on the local
network instead of the internet IP



Miha Pihler [MVP] wrote:
> Can you also check if this will help...
>
> Cannot access shares or printers across the LAN from Windows XP
> http://support.microsoft.com/kb/841570
>
> --
> Mike
> Microsoft MVP - Windows Security
>
> "Frank J. Reashore" <(E-Mail Removed)> wrote in message
> news:e%(E-Mail Removed)...
> > Miha,
> >
> > Thanks for your response.
> >
> > I did use the DNS form of the domain name, mydomain.local, when I tried to
> > join the domain.
> >
> > I also logged in to the security dialog using
> > (E-Mail Removed)l.
> >
> > Both tests to access $C failed with the message "No network provider
> > accepted the given network path".
> >
> > Interesting, however I can still ping 192.168.2.2 successfully.
> >
> > Regards,
> > Frank
> >
> >
> > "Miha Pihler [MVP]" <mihap-(E-Mail Removed)> wrote in message
> > news:%(E-Mail Removed)...
> >> Hi,
> >>
> >> few things to try.
> >>
> >> What did you enter as name of domain to join? Did you enter NetBIOS name
> >> or DNS name? Try DNS name e.g. mydomain.local
> >>
> >> What happens if you try this on the client? Click Start -> Run and enter
> >>
> >> \\vancouver\c$
> >>
> >> What happens if you enter this:
> >>
> >> \\192.168.2.2\c$
> >>
> >> --
> >> Mike
> >> Microsoft MVP - Windows Security
> >>
> >>
> >> "Frank J. Reashore" <(E-Mail Removed)> wrote in message
> >> news:(E-Mail Removed)...
> >>> Mike,
> >>>
> >>> Thanks for your response.
> >>>
> >>> Everything you said in your email made perfect sense. I have included
> >>> "ipconfig /all" results for the DC and client virtual PCs respectively
> >>> at the bottom of this message.
> >>>
> >>> I believe you can verify (see below) that my network connection is
> >>> exactly as you had suggested.
> >>>
> >>> The problem is that when I try to join the client to the domain I get a
> >>> "Windows cannot find the network path" error. Note, I logged in as
> >>> (E-Mail Removed)l
> >>>
> >>> I ensured that my DC was rebooted.
> >>>
> >>> Also, I am able to ping the DC from the client.
> >>>
> >>> Cheers,
> >>> Frank
> >>>
> >>>
> >>> --------------------------------------------------------------------------------------------------------------
> >>>
> >>> Windows IP Configuration
> >>>
> >>> Host Name . . . . . . . . . . . . : vancouver
> >>> Primary Dns Suffix . . . . . . . : mydomain.local
> >>> Node Type . . . . . . . . . . . . : Unknown
> >>> IP Routing Enabled. . . . . . . . : No
> >>> WINS Proxy Enabled. . . . . . . . : No
> >>> DNS Suffix Search List. . . . . . : mydomain.local
> >>>
> >>> Ethernet adapter Local Area Connection:
> >>>
> >>> Connection-specific DNS Suffix . :
> >>> Description . . . . . . . . . . . : Intel 21140-Based PCI Fast
> >>> Ethernet Adapter (Generic)
> >>> Physical Address. . . . . . . . . : 00-03-FF-1C-3E-38
> >>> DHCP Enabled. . . . . . . . . . . : No
> >>> IP Address. . . . . . . . . . . . : 192.168.2.2
> >>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> >>> Default Gateway . . . . . . . . . : 192.168.2.1
> >>> DNS Servers . . . . . . . . . . . : 127.0.0.1
> >>>
> >>>
> >>> Windows IP Configuration
> >>>
> >>> Host Name . . . . . . . . . . . . : toronto
> >>> Primary Dns Suffix . . . . . . . :
> >>> Node Type . . . . . . . . . . . . : Mixed
> >>> 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-15-3E-38
> >>> DHCP Enabled. . . . . . . . . . . : No
> >>> IP Address. . . . . . . . . . . . : 192.168.2.120
> >>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> >>> Default Gateway . . . . . . . . . : 192.168.2.1
> >>> DNS Servers . . . . . . . . . . . : 192.168.2.2
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> "Miha Pihler [MVP]" <mihap-(E-Mail Removed)> wrote in message
> >>> news:%(E-Mail Removed)...
> >>>> Hi,
> >>>>
> >>>> Check DNS settings on both virtual computers. IPconfig results that you
> >>>> posted here did not show all the ipconfig settings. You should do
> >>>>
> >>>> ipconifg /all
> >>>>
> >>>> on all your computers and post here. The result will also show DNS and
> >>>> other settings.
> >>>>
> >>>> In general domain controller must also use Active Directory DNS (and
> >>>> _not_ e.g. ISP DNS server). So set the domain controller to point back
> >>>> to itself. You could enter 192.168.2.2 under preferred DNS server or
> >>>> even better 127.0.0.1. Now restart NetLogon service on DC.
> >>>> Now change preferred DNS settings on your virtual client that you would
> >>>> like to join to domain "mydomain.local" to point to 192.168.2.2 (not --
> >>>> here you can't use 127.0.0.1 since there is no DNS installed on this
> >>>> server).
> >>>>
> >>>> Now try to join your virtual client to mydomain.local domain.
> >>>>
> >>>> Note: in general it is not best practice to use "mydomain.local" for
> >>>> production Active Directory DNS name.
> >>>>
> >>>> --
> >>>> Mike
> >>>> Microsoft MVP - Windows Security
> >>>>
> >>>> "Frank J. Reashore" <(E-Mail Removed)> wrote in message
> >>>> news:(E-Mail Removed)...
> >>>>>I have two virtual PCs (running Win2003 Enterprise SP1) hosted on my
> >>>>>home WinXP Pro SP2 (which is connected to my ISP). I am trying to
> >>>>>create a domain of the virtual PCs, but am encountering problems
> >>>>>joining the second virtual PC to the domain.
> >>>>>
> >>>>> I converted the IP address of one Virtual PC to static, promoted it to
> >>>>> a domain controller, and installed DNS. I named the new domain
> >>>>> "mydomain.local".
> >>>>>
> >>>>> Note also that I have assigned distinct names to each to each of the
> >>>>> virtual machines.
> >>>>>
> >>>>> The second virtual PC has a dynamic IP address and belongs to
> >>>>> WORKGROUP.
> >>>>>
> >>>>> I am able to ping the virtual domain controller from the virtual
> >>>>> client machine. My exact network configuration is shown at the bottom
> >>>>> of this message.
> >>>>>
> >>>>> When I attempt to join the client virtual PC to the domain (via
> >>>>> Control Panel => System =>
> >>>>> Computer Name => Change.), I get the standard login prompt (to which I
> >>>>> enter (E-Mail Removed)l and password). However, I then get
> >>>>> the following error:
> >>>>>
> >>>>> --------------------------------------------------------------------------------------
> >>>>> The following error occurred when DNS was queried for the service
> >>>>> location (SRV) resource record used to locate a domain controller for
> >>>>> domain mydomain.local:
> >>>>>
> >>>>> The error was: "DNS name does not exist."
> >>>>> (error code 0x0000232B RCODE_NAME_ERROR)
> >>>>>
> >>>>> The query was for the SRV record for
> >>>>> _ldap._tcp.dc._msdcs.mydomain.local
> >>>>>
> >>>>> Common causes of this error include the following:
> >>>>>
> >>>>> - The DNS SRV records required to locate a domain controller for the
> >>>>> domain are not registered in DNS. These records are registered with a
> >>>>> DNS server automatically when a domain controller is added to a
> >>>>> domain. They are updated by the domain controller at set intervals.
> >>>>> This computer is configured to use DNS servers with following IP
> >>>>> addresses:
> >>>>>
> >>>>> 192.168.2.1
> >>>>>
> >>>>> - One or more of the following zones do not include delegation to its
> >>>>> child zone:
> >>>>>
> >>>>> mydomain.local
> >>>>> local
> >>>>> . (the root zone)
> >>>>>
> >>>>> --------------------------------------------------------------------------------------
> >>>>>
> >>>>> This error is occurring because my virtual client is using the DNS of
> >>>>> my ISP and it is not able to "delegate" the join request to the
> >>>>> "mydomain.local" domain.
> >>>>>
> >>>>> Alternatively, I have tried to configure my client virtual machine to
> >>>>> use the DNS of the virtual domain controller but that also leads to
> >>>>> different errors.
> >>>>>
> >>>>> So my question is: How do I configure my setup so that the join
> >>>>> request for the domain from the virtaul client is successfully passed
> >>>>> to the virtual domain controller?
> >>>>>
> >>>>> Thanks in advance for any help.
> >>>>>
> >>>>> Regards,
> >>>>> Frank J. Reashore, MCSD.net, MCDBA
> >>>>>
> >>>>> Vancouver, Canada
> >>>>>
> >>>>> ************************************************** ******
> >>>>>
> >>>>> Windows XP Pro (Host PC + WORKGROUP)
> >>>>>
> >>>>> Connection-specific DNS Suffix . : bc.hsia.telus.net
> >>>>> IP Address. . . . . . . . . . . . : 192.168.2.117 (dynamic)
> >>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> >>>>> Default Gateway . . . . . . . . . : 192.168.2.1
> >>>>>
> >>>>> Windows Server 2003 Enterprise (Virtual PC + Domain controller + DNS +
> >>>>> domain = mydomain.local)
> >>>>> Connection-specific DNS Suffix . :
> >>>>> IP Address. . . . . . . . . . . . : 192.168.2.2 (static)
> >>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> >>>>> Default Gateway . . . . . . . . . : 192.168.2.1
> >>>>>
> >>>>> Windows Server 2003 Enterprise (Virtual PC + Client + WORKGROUP)
> >>>>> Connection-specific DNS Suffix . :
> >>>>> IP Address. . . . . . . . . . . . : 192.168.2.120 (static)
> >>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> >>>>> Default Gateway . . . . . . . . . : 192.168.2.1
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>
> >>>
> >>
> >>
> >
> >