New Windows 2008 Server domain connection problem

I am trying to setup a test network. I just installed windows server 2008
enterprise and it seems to be functioning fine. Two other computers (both
using vista ultimate on a workgroup) can see and access a share I setup on
the server.

The problem is I want to add both Vista machines to the domain. When I go
through the steps to add them, I get an error message that says network path
not available.

I can ping the server both by address and by name. I can browse the vista
machines from the server.

I must have missed something in the setup, but don't know what. The server
has AD, DNS, File Server, Print Server roles enabled.

Any suggestions.

WB

"w" <(E-Mail Removed)> wrote in message
news:u6y8FX2#(E-Mail Removed)...
> I am trying to setup a test network. I just installed windows server 2008
> enterprise and it seems to be functioning fine. Two other computers (both
> using vista ultimate on a workgroup) can see and access a share I setup on
> the server.
>
> The problem is I want to add both Vista machines to the domain. When I go
> through the steps to add them, I get an error message that says network
> path not available.
>
> I can ping the server both by address and by name. I can browse the vista
> machines from the server.
>
> I must have missed something in the setup, but don't know what. The
> server has AD, DNS, File Server, Print Server roles enabled.
>
> Any suggestions.
>
> WB

Are the Vista machines set to use the DC for DNS? What happens if you
open a command prompt and do an nslookup on the domain name?

"w" <(E-Mail Removed)> wrote in message news:u6y8FX2%(E-Mail Removed)...
>I am trying to setup a test network. I just installed windows server 2008
> enterprise and it seems to be functioning fine. Two other computers (both
> using vista ultimate on a workgroup) can see and access a share I setup on
> the server.
>
> The problem is I want to add both Vista machines to the domain. When I go
> through the steps to add them, I get an error message that says network path
> not available.
>
> I can ping the server both by address and by name. I can browse the vista
> machines from the server.
>
> I must have missed something in the setup, but don't know what. The server
> has AD, DNS, File Server, Print Server roles enabled.
>
> Any suggestions.
>
> WB
>

The problem you've described is a classic DNS issue, or rather a classic issue of not using the DC as the only DNS address in the client's IP properties.

As Bill asked, are the Vista machines using the DC as it's only DNS address in their IP properties, or is there an ISP's or the router as a DNS address?

If not, if they are using an ISP's DNS, or the router as a DNS address, they MUST be removed and only have the DC as a DNS address in their properties. If they are getting an automatic address from DHCP, such as from the router, then that must be adjusted to not provide the ISP's DNS or the router as an IP address. If the router cannot be setup to do this, such as a Verizon ActionTec, then I suggest to disable the router's DHCP service, and setup DHCP on the server so you have better control.

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and confers no rights.

Please reply back to the newsgroup/forum to benefit from collaboration among responding engineers, as well as to help others benefit from your resolution.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
Microsoft Certified Trainer
(E-Mail Removed)
http://twitter.com/acefekay

For urgent issues, you may want to contact Microsoft PSS directly. Please check http://support.microsoft.com for regional support phone numbers.

Yes, everything (including) the server is behind my router and the router is
setup with DHCP. I will work through your suggestions. I think I will just
setup DHCP on the Server and bypass the router altogether.

wb

"Ace Fekay [Microsoft Certified Trainer]" <(E-Mail Removed)>
wrote in message news:%23voSKP5%(E-Mail Removed)...
"w" <(E-Mail Removed)> wrote in message
news:u6y8FX2%(E-Mail Removed)...
>I am trying to setup a test network. I just installed windows server 2008
> enterprise and it seems to be functioning fine. Two other computers (both
> using vista ultimate on a workgroup) can see and access a share I setup on
> the server.
>
> The problem is I want to add both Vista machines to the domain. When I go
> through the steps to add them, I get an error message that says network
> path
> not available.
>
> I can ping the server both by address and by name. I can browse the vista
> machines from the server.
>
> I must have missed something in the setup, but don't know what. The
> server
> has AD, DNS, File Server, Print Server roles enabled.
>
> Any suggestions.
>
> WB
>

The problem you've described is a classic DNS issue, or rather a classic
issue of not using the DC as the only DNS address in the client's IP
properties.

As Bill asked, are the Vista machines using the DC as it's only DNS address
in their IP properties, or is there an ISP's or the router as a DNS address?

If not, if they are using an ISP's DNS, or the router as a DNS address, they
MUST be removed and only have the DC as a DNS address in their properties.
If they are getting an automatic address from DHCP, such as from the router,
then that must be adjusted to not provide the ISP's DNS or the router as an
IP address. If the router cannot be setup to do this, such as a Verizon
ActionTec, then I suggest to disable the router's DHCP service, and setup
DHCP on the server so you have better control.

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup/forum to benefit from collaboration among
responding engineers, as well as to help others benefit from your
resolution.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
Microsoft Certified Trainer
(E-Mail Removed)
http://twitter.com/acefekay

For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

"w" <(E-Mail Removed)> wrote in message news:%23EfHn7%23%(E-Mail Removed).. .
> Yes, everything (including) the server is behind my router and the router is
> setup with DHCP. I will work through your suggestions. I think I will just
> setup DHCP on the Server and bypass the router altogether.
>
> wb

Sounds like an excellent plan. You will have complete control of DHCP, especially in an AD infrastructure, no matter how small or large.

Ace