Installing RIS on Server 2003

December 20, 2010 at 16:56:43
Specs: server 2003, 2.ghz / 1gb
Hi, im new to this, just need a little help.

I have 2 servers running W2k3

1st is my PDC and has, DHCP, AD & DNS
2nd is a Member Server connected to my DC, no problem.

Im trying to use the Member server as a RIS.

I installed the RIS software from add/remove windows components, but when I double click Remote Installation Services Setup Wizard and click next, I get

"Domain Unavailable. RIS Setup cannot obtain informaiton from a domain controller. Either the domain controller is not available, the current user doen not have permission to acces the Domain, this computer is not a member server in the domain, or this computer is joined to a workgroup instead of a domain" and wont let me install.

Im logged in as the Admin on the Member Server, but when I right click on the Remote Installation Services Setup Wizard, select run as (then the "following user" radio button) and use the Domain Controllers Credentials = hive.local\administrator, then my password, it lets me install... why is this ?

Is it because Im logged on as local admin on my member server and dont have domain admin privlages to install the software, if so, how can I configure my DC to allow the admin to install with Remote Installation Services Setup Wizard or is this normal and should I just use run as ?

Thanks


See More: Installing RIS on Server 2003

Report •

#1
December 21, 2010 at 12:58:06
what is this member server pointed at for dns?
post the results of a nslookup yourDCname from this member server for review

Answers are only as good as the information you provide.
How to properly post a question:


Report •

#2
December 22, 2010 at 13:35:44
The member server is pointing to the PDC on a static I.P = 192.168.2.50.

Im not familiar with Nslookup,

But when I type Nslookup in command promt of the member server I get ...

DNS request timed out.
timeout was 2 seconds.
*** can't find server name for 192.168.2.50: Timed out
Default Server: Unknown
Address: 192.168.2.50

If I type Nslookup hive.local (MY DC) on theh member server

I get...

Server: hive.local
Address: 192.168.2.250
*** hive.local can't find nslookup: Non-existent domain


Report •

#3
December 22, 2010 at 14:20:08
Clearly your dns setup isn't correct. This may be due to relating AD to NT in your thinking. There are no pdc/bdcs in AD

hive.local is your domain name.
try the DC servers name when at the DC

Answers are only as good as the information you provide.
How to properly post a question:


Report •

Related Solutions

#4
December 22, 2010 at 16:13:06
sorry my bad, told you I was new to this.

I assumed that as its the only DC it was called a primary domain controller.
I didn't realise that it was pre-2000, Sorry.

Its just W2k3 server as a DC that has... Active Directory, DNS and DHCP.
I then installed w2k3 server on another system and Joined it the domain hive.local.

And sorry I miss read, when you asked about my DC name, my daughter was jumping all over me. I'll post the results in the morning.
Thankyou for your time and patience :-)
Oh, I can set up users on the DC and access the Domain on other Pc's with no problem, if that helps.


Report •

Ask Question