Re: Adding PC to SBS 2000 domain



After you joined the PC to the domain, did you immediately reboot and log
onto the domain (not the local PC)?

--
Merv Porter [SBS-MWP]
============================

"James Newman" <jnewman33@xxxxxxxxx> wrote in message
news:3eo0g2lvkhhv4opccsh8squtn2q11ki5s8@xxxxxxxxxx
Hey all,

I have what I hope to be a very simple scenario and a question.


I have a customer with SBS 2000 server w/ 1 nic
There are three workstations that have been working fine for years.

One of the workstations suffered a total HD failure and I have
replaced the PC with a whole new machine with a fresh install of WinXp
Pro.

I have inherited this network and my knowledge is based/limited to SBS
2003.


On the SBS 2000 server I created and new user account and new computer
account. After cabling the new workstation I used the Network ID
wizard in XP to join the computer to the domain. All prompts were as
expected and got the welcome to the domain message. I then set up
their network aware medical management software. Tested the setup and
went home.

Customer used that setup succesfully for the rest of the day.

Next morning however it seems that the workstation can see the server
but not the shares. If I click on the server in network neighborhood
it waits for a minute and asks for authentication. Giving that users
credentials the server responds with something about that users
credentials haveing already been tried and there is no other domain
controller to use.

To solve the problem is change the PC to peer mode then back to domain
mode using the network ID wizard in XP. Everything is working again
for the rest of the day.

Next morning the whole scenario repeats itself.


Customer is now HIGHLY irritated and I am at a loss. The other two
workstations continue to work as normal.

Is there a better way to join a fresh PC to the domain other that what
I did ? Did the ConnectComputer wizard exist in SBS 2000?


Any ideas would be greatly appreciated.


Thanks as always,

James Newman



.



Relevant Pages

  • Re: OT: all systems on network slow for last week or so
    ... While troubleshooting a problem with LogMeIn disconnecting behind WatchGuard firewalls, I found out that my workstations had it enabled, when I thought I had killed it at the same time I killed it on my server after my SBS 2003 SP2 update. ... and SP3 workstations on a client's SBS 2003 SP2 network are slow. ...
    (microsoft.public.windows.server.sbs)
  • Re: Server/Network setup question
    ... Let's keep the P2P network and the ... SBS server's internal NIC to the switch. ... The internal NIC of the SBS server will default to 192.168.16.2 during the ... you change the IP of the rented printer to 192.168.16.8 (or some ...
    (microsoft.public.windows.server.sbs)
  • Re: DHCP Fails on Authorized Server
    ... The DHCP shutdowns may because the SBS detects another DHCP in network. ... How to configure Internet access in Windows Small Business Server 2003 ... On the Connection Type page, click Broadband, and then click Next. ...
    (microsoft.public.windows.server.sbs)
  • RE: Problems with Permissions
    ... And SBS server is only take ... the role of an internal server. ... they are all configured to connected to internal network. ... g. Run the Configure Email and Internet Connection Wizard on SBS server. ...
    (microsoft.public.windows.server.sbs)
  • Re: ISA Server & a WiFi Hotspot (some DHCP for good measure too)
    ... ISA2k4 is currently not supported on SBS ... To review - you have LAN clients that you want to have ... card for your server. ... > network with 5 client computers. ...
    (microsoft.public.windows.server.sbs)