Networks

Ask something
Discussion Locked

Setting up Server/Client

0 helpful
16 replies

by woolly.watson

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi,

I am a fairly new student of the MCSE course and require some assistance in setting up a test client/sever environment at home.

I am trying to do this at present using a Windows Server 2003 machine and a Windows XP machine.

I have assigned the Domain Controller (Active Directory) and DNS Server Roles.

Created User account and client computer within Active Directory.

In System Properties on Client PC I have renamed the computer to join the domain. I have then input the name of the domain in the relevant field and am presented with User Name and Password box for accounts with permission to join domain. In this box I enter the logon name XXX@Woolly.Watson.Domain and the password created for the user account.

At this stage I am presented with various messages 'Access is Denied' 'Network Path Not Found'

In trying to resolve this issue I have pinged the DNS Server and IP address of Server 2003 Machine sucessfully. I have ensured that in TCP/IP Protocol on both client/sever that the preferred DNS Server is specified and the IP address is Static( I think??).

I have also disabled my firewall.

Is there some procedure I have not carried out so far??Not sure what else to do at present.. Your advice would be appreciated.

many thanks
Lee

16 replies

by woolly.watson

Thanks for the advice although it did not work I got different results. 'Unknown username of Bad Password'

by rkuhn040172

Just the user name such as Admin and then password. If that doesn't work, use domain name\user name and then password.

For example:

home\rickk
password

by woolly.watson

Thanks for the advice although it did not work I got different results. 'Unknown username of Bad Password'

by nz_justice

Use your admin account to join the computer to the domain. The user login you created would not have sufficient enough rights to add the computer to the domain. You could also add your created user to the domain admins account to enable your user to add computers to your new domain.

by woolly.watson

Use your admin account to join the computer to the domain.
Do you mean admin account on XP machine? If so I am logged on as an administrator.

The user login you created would not have sufficient enough rights to add the computer to the domain. You could also add your created user to the domain admins account to enable your user to add computers to your new domain.

I have added my created user to domain admins. Can you please clarify what I need to do next as I have already added the client PC in previously. Sorry If I'm appearing a little dull this is a bit of a steep learning curve.

by cmiller5400

Hmmmmm... In DNS did you set up a in-addr.arpa to resolve ip addresses into names? Can you nslookup the hostname from the xp station? such as "nslookup Woolly.Watson.Domain" assuming your server is called woolly?

You should be logged into the XP station as an administrator. then when you try to add the station to the active directory domain, you enter your credentials. What are you putting in the domain box when you change the XP station from workgroup to domain. It should be just domain name, not servername.domain.yyy ex domain.yyy

"The user login you created would not have sufficient enough rights to add the computer to the domain. You could also add your created user to the domain admins account to enable your user to add computers to your new domain."

Well kind of true, all user accounts by default in Active directory have the rights to add up to 10 workstations before requiring the right to add workstations to the domain.

by woolly.watson

Hi, I do not recall setting up a in-addr.arpa to resolve IP addresses into names. Is this something I can do post installation? If so how do i do that?

I have tried nslookup and get error message returned saying non existent domain. In the domain box I am entering my logon name as set up as user on Windows Server 2003 this is also the same as my netbios name - Lee. Only when I enter this in the domain box do I get the password box to come up. If I enter my full domain name Lee.Watson.Domain I get message saying Domain Controller could not be contacted.

Thanks for your help and advice so far.

by rkuhn040172

Comment from Woolly.Watson on 05/03/06:
Thanks for the advice although it did not work I got different results. 'Unknown username of Bad Password'

Make sure you are using the user name and password of the domain administrator (or an account with sufficient priviledges to add computers to the domain) and NOT the admin account of the local XP PC.

by woolly.watson

In DNS I do not recall setting up a in-addr.arpa to resolve Ip adresses. i sthis something I can do post installation and if so how?

NS Lookup is unsuccessful on XP machine returning a message of non existent domain.

by cmiller5400

I read your comments to my last post and you stated that your username is the same as your netbios name? Is your workstation named "Lee" as well as your account? If so, that could be causing an issue because when you try to join the domain, it tries to create a computer account in active directory with the name of the station in the Computers container off of the root. Try renaming your station to something else.

As far as the in-addr.arpa, you can create it post install in dns management. In your Reverse Lookup zone create a new zone for it. When the network id box comes up, enter the first 3 octets of your IP address scheme.

by woolly.watson

Hi

My XP computer name that i have added to active directory is different from that of my logon name. However my Logon name created for XP machine in Active Diectory is the same as my administrator sign on for XP Machine.

I have created new reverse lookup zone adding Ip address 192.168.1 which is the first 3 octets of IP address on my Server2003 machine. After this I tried NSLOOKUP again on XP machine and got the same message. However I note that it states address 194.168.8.100. Shouldn't the IP address of both machines be the same apart from the last octet?

Also do you think that it may cause any issues with the fact that both PC's are plugged directly into a router?

Don't really understand this rating stuff either. If I select Acceptable does that close my question?

Thanks Again....

by woolly.watson

Hi

My XP computer name that i have added to active directory is different from that of my logon name. However my Logon name created for XP machine in Active Diectory is the same as my administrator sign on for XP Machine.

I have created new reverse lookup zone adding Ip address 192.168.1 which is the first 3 octets of IP address on my Server2003 machine. After this I tried NSLOOKUP again on XP machine and got the same message. However I note that it states address 194.168.8.100. Shouldn't the IP address of both machines be the same apart from the last octet?

Also do you think that it may cause any issues with the fact that both PC's are plugged directly into a router?

Don't really understand this rating stuff either. If I select Acceptable does that close my question?

Thanks Again....

by conrad.delacruz

Odd...

Set up DHCP...

In here it will give you the option to give your domain a netbios name...so, usually for company.com I make the netbios comapany...

then when I join the domain, i just put company in the domain field...

username and password that wahlah..

Its telling you invalid user name and password because you either cant remember the credentials or its the wrong domain or non existant...

also, make sure your server IP is static...

by conrad.delacruz

Odd...

Set up DHCP...

In here it will give you the option to give your domain a netbios name...so, usually for company.com I make the netbios comapany...

then when I join the domain, i just put company in the domain field...

username and password that wahlah..

Its telling you invalid user name and password because you either cant remember the credentials or its the wrong domain or non existant...

also, make sure your server IP is static...

This discussion is closed to new replies.