Proper client setup for domain name resolution in AD

  • Thread starter Thread starter William Oliveri
  • Start date Start date
W

William Oliveri

Hi all,
I have a AD server setup with DNS all working fine.

My question is regarding how the client should be setup to resolve the
domain name in order to join the domain.

I have one XP machine and many 95 machines on this network to join a W2K
server.

I'd like to run only TCP/IP (Not run NetBUEI) in this network.

My tests at home with XP and W2K WS I find I need to put the ip address in
the primary DNS setting on the client to resolve the domain to join it.

First question: Is this the correct procedure to put the IP of the DNS
Server in the Primary DNS Setting of the TCP/IP settings on the client to
join the domain or should I be able to resolve the domain name without this?

Second question: How is this handled in Win95? Do I need to put an entry in
the LMHosts file to resolve the domain for win95?


Thanks for any suggestions/help.

Bill
 
Hi all,
I have a AD server setup with DNS all working fine.

My question is regarding how the client should be setup to resolve the
domain name in order to join the domain.

I have one XP machine and many 95 machines on this network to join a W2K
server.

I'd like to run only TCP/IP (Not run NetBUEI) in this network.

My tests at home with XP and W2K WS I find I need to put the ip address in
the primary DNS setting on the client to resolve the domain to join it.

First question: Is this the correct procedure to put the IP of the DNS
Server in the Primary DNS Setting of the TCP/IP settings on the client to
join the domain or should I be able to resolve the domain name without this?

Second question: How is this handled in Win95? Do I need to put an entry in
the LMHosts file to resolve the domain for win95?
Click to expand...
Use DHCP if you don't already.

Cheers,

Cliff
 
I'm not using DHCP and this is not my network so I can't implement DHCP at
this time. Probably in the future we can do this.

Without using DHCP what would be the answer to my questions.

Thank you,

Bill
 
DHCP will make it soooooo much easier. It sets up DNS servers, IP
addressses, default gateways so that you don't have to visit all
machines.....

If you HAVE to do it manually, set the internal DNS setting on the
client to the DNS address of the DNS server. It will NOT automatically
find it.

The LMHosts file is for Netbios name resolution. The hosts file is for
Domain Name resolution.

If the 95 clients are vanilla, they will not be able to take part in
the AD Domain. I believe that there is an AD client for Win95.

However, I don't believe that you will be able to go TCP/IP only if
you have 95 clients. You will have to, as a minimum, use NetBeui over
TCP/IP, I believe.

Cheers,

Cliff

I'm not using DHCP and this is not my network so I can't implement DHCP at
this time. Probably in the future we can do this.

Without using DHCP what would be the answer to my questions.

Thank you,

Bill
Click to expand...
 
Thanks Cliff,

What do you mean that Win95 won't be able to take part in the AD Domain?
Do you mean they cannot join the domain or that they won't be able to have
group policy applied which I'm aware.

Thanks again,
Bill

Enkidu said:
DHCP will make it soooooo much easier. It sets up DNS servers, IP
addressses, default gateways so that you don't have to visit all
machines.....

If you HAVE to do it manually, set the internal DNS setting on the
client to the DNS address of the DNS server. It will NOT automatically
find it.

The LMHosts file is for Netbios name resolution. The hosts file is for
Domain Name resolution.

If the 95 clients are vanilla, they will not be able to take part in
the AD Domain. I believe that there is an AD client for Win95.

However, I don't believe that you will be able to go TCP/IP only if
you have 95 clients. You will have to, as a minimum, use NetBeui over
TCP/IP, I believe.

Cheers,

Cliff
Click to expand...
 
Win95 clients will not "join" a Domain. They won't have machine
accounts. They won't have group policy. They CAN access Domain
resources if the user connects to the resource with a Domain User and
password.

See this discussion. particular Wingback's contribution and the
replies. I'm sure there's a better reference somewhere.

http://x220.win2ktest.com/forum/topic.asp?TOPIC_ID=2144

Cheers,

Cliff

Thanks Cliff,

What do you mean that Win95 won't be able to take part in the AD Domain?
Do you mean they cannot join the domain or that they won't be able to have
group policy applied which I'm aware.

Thanks again,
Bill
Click to expand...
 
Hey, thanks.

Yes, I had read that a little earlier but what's the exact entry for SMB
(Server Message Block) in security settings?

What are the line item names to turn this off.

Thanks,

Bill



Enkidu said:
Win95 clients will not "join" a Domain. They won't have machine
accounts. They won't have group policy. They CAN access Domain
resources if the user connects to the resource with a Domain User and
password.

See this discussion. particular Wingback's contribution and the
replies. I'm sure there's a better reference somewhere.

http://x220.win2ktest.com/forum/topic.asp?TOPIC_ID=2144

Cheers,

Cliff
Click to expand...
 
Sorry! You'll have to hope someone else replies. Or maybe have a look
at www.microsoft.com.

Cheers,

Cliff

Hey, thanks.

Yes, I had read that a little earlier but what's the exact entry for SMB
(Server Message Block) in security settings?

What are the line item names to turn this off.

Thanks,

Bill
Click to expand...
 
Hi William. Back to your original questions:

- Yes, your XP machines should point to your internal DNS server(s) in
their TCP/IP settings (as opposed to pointing to your ISP, set up forwarders
on your DNS server for this).

- Win9x clients will use NetBIOS name resolution....you can do this with
either LMHOSTS files or a WINS server. See the following article for
information on creating lmhosts files:

http://support.microsoft.com/default.aspx?scid=KB;EN-US;180094

If your domain is Windows 2000, then Win95 clients should be able to log on
w/ domain accounts. In a Windows 2003 domain, SMB signing is enabled by
default and Win95 clients will not be able to log on. The solution is to
either install the dsclient on the Win95 machines or disable SMB signing in
the default domain controllers policy. I would strongly recommend
installing the dsclient on all Win9x machines in the domain regardless of
SMB signing/2003.

For more information on the Win95/SMB signing subject, see the following
article:

http://support.microsoft.com/default.aspx?scid=KB;EN-US;325379


--
Jimmy Harper [MSFT]
Directory Services
This posting is provided "AS IS" with no warranties, and confers no rights

Enkidu said:
Sorry! You'll have to hope someone else replies. Or maybe have a look
at www.microsoft.com.

Cheers,

Cliff
Click to expand...
 
Back
Top