Link to home
Start Free TrialLog in
Avatar of sbcw
sbcw

asked on

Windows 2003 Server setup mistake

Learning the hard way here...We setup a brand new Windows 2003 Server.  The mistake made was made when it came time to enter a qualified domain name for the new server.  We entered a .com domain which doesnt exist.  Now we got quite a few dns errors of course.

We probably sould have used something like doman.local instead of domain.com, but now is it too late? Is there a way to save this setup or shold we begin from scratch again?
Avatar of Network_Data_Support
Network_Data_Support
Flag of United Kingdom of Great Britain and Northern Ireland image

is this just a member server?


Avatar of sbcw
sbcw

ASKER

It is.  Only for file sharing and one network app.
ASKER CERTIFIED SOLUTION
Avatar of Brian Pierce
Brian Pierce
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I assume you are adding this server to an existing domain then ?
just  promote it to the correct domain in computer propities
Avatar of sbcw

ASKER

KCTS: We dont actually have a real domain - just an internal server.
so you want to use a work group?   or you are setting up a DC
So how come you were asked for a qualifed domain name.

Please explain your situation fully, what you have done in detail, and what you are trying to achieve
Avatar of sbcw

ASKER

We need a server to run a network app. and share files.  We want users to have server accounts. We do not have a domain at this time. Thats about as simple as I can say it.,
well depending on how many users you have you either want to setup a  domain controller to manage ACL and user accounts so then you can join users to the network
So you have installed windows ?
You have given the machine a name ?
I need to know where you entered the qualified domain name - on which screen so I know what you have done