Client takes ages to log on

[Martyuk39]

I've just built a Windows 2003 server with an evaluation copy of Windows 2003 Enterprise Edition. I ran the wizard to install DHCP, DNS, Active Directory etc and made no changes [edit - I've installed SP1]

I've set up a laptop running Win2K and had difficulty joining the domain - got messages like "The Trust relationship between this workstation and the primary domain failed" but eventually I was able to connect. However upon rebooting it took about 45 minutes to get from POST to the desktop. So it's obviously not right. The machines can ping each other - well, about 80% of the time anyway.

I'm looking for an easy guide - first of all, how do I know if my server is set up correctly? Big question I know. I have users set up in AD but I don't set up computers in AD - the idea is that they'll be added when I join the machines to the domain - have I got that bit right?

I'm new to 2003 server - most of my experience is in NT4 and I've recently started an MCSE in 2003. So a lot of the terminology is slightly alien to me. And the procedures. If someone could point me in the right direction to get started I'd be very grateful. I guess specs could be important - here they are:

Server: Asus A7N8X-VM400, Athlon XP3000, 512MB RAM, 160GB IDE with 8MB cache
Laptop: Gateway Solo 450Mhz, 128MB, about 5GB I think - old and slow I know but connects to my NT4 domain at work very nicely.
5-port switching hub - cost £8
Server also connects by wire to a Netgear DG834G wireless router (put an additional NIC in the server)
My company's probably going to go under in a month or 2 hence my trying to drag my skills into the third millenium.
Thanks
Martin

 

[Wizkid]

Yes, computers will be added to AD automatically when you join the domain.

Do you have the primary DNS for the laptop pointing to the win2k3 server? AD is very dependent on DNS to work properly.

 

[Martyuk39]

Thanks - could you tell me how I check whether the primary DNS for the laptop is pointing to the win2k3 server?

 

[loup garou]

Originally posted by: Martyuk39
Thanks - could you tell me how I check whether the primary DNS for the laptop is pointing to the win2k3 server?

start>run>cmd>ipconfig /all
Check the first ip in the DNS servers list.

 

[Martyuk39]

Thanks - I'll check that. Currently it's taking so long to get to the desktop so it'll take a while. I guess there's no getting round that is there?

 

[SectorZero]

Start => Run => CMD

c:\ipconfig/all

Primary DNS Server should be your Domain controller

 

[Martyuk39]

Got there in the end....and my domain is called TEST - is the following what I should expect?



Windows 2000 IP Configuration



Host Name . . . . . . . . . . . . : MEGAN
Primary DNS Suffix . . . . . . . : Test.local
Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : Test.local

Ethernet adapter Local Area Connection 5:



Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Linksys EtherFast 10/100 USB Network Adapter #2
Physical Address. . . . . . . . . : 00-04-5A-07-B0-77

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.0.10

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.0.1

DHCP Server . . . . . . . . . . . : 192.168.0.1

DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : 08 April 2005 14:05:33

Lease Expires . . . . . . . . . . : 18 April 2005 17:05:33

 

[Woodie]

This doesn't look right. Your DNS and DHCP servers are the same as your default gateway, making me think you left DHCP running on your gateway, as well as your DC. If so, then:

Turn off DHCP in your router. Then get new DHCP settings (cmd: ipconfig /renew)
That should get the workstation to register in the AD DNS and use the AD as the primary DNS and DHCP server. This will make your domain *much* happier.

 

[Martyuk39]

I have the DC on which I ran the wizard to configure amongst other things DNS and DHCP, and a 5-port switch hub, not a router, which isn't a DHCP server. The router I mentioned is for internet connectivity and the DC connects to it via a seperate network card. I don't think I want to turn off DHCP on this router - that's not what you're talking about is it?

It doesn't take much to confuse me, as you've seen!

 

[Woodie]

Well, your default gateway is the 0.1, which is also your DNS/DHCP. That is your server?
OK, if that is the case, I understand the addresses now. That's a very complicated network setup for a non-expert. Triple check your routing statements on the server...I wonder if the replies are being sent to the wrong subnet.
Do you have Routing & RAS configured on the server? (see above)
Is the server set to request a DHCP address on the outside NIC? If so, I'd switch it to manual if I were you. (Part of the routing stuff above)

 

[Martyuk39]

I'm lost now. I guess I shouldn't have just run the wizard and tried to figure it out bit by bit instead.

OK how do I check the routing statements on the server? Is that just using ping? The server is obtaining an address on the outside NIC from the router. You're saying to switch to a manual address?

Do you think it might be worth my while just re-running the server installation and not running any wizards and perhaps coming back here for advice?

 

[Colebert]

make your router your gateway and,

make your W2K3 server your DHCP server.
--configure DHCP to give the router as the gateway
--configure DHCP to give the server as the DNS
--configure DNS to forward internet naming to your ISP's DNS

**or**

give each client a static IP w/ the router as the gateway and server as DNS

 

[Martyuk39]

I'll try all that - might take me a little while, I'll let you know.
Cheers

[EDIT]

I'm going to start again from scratch, not enabling anything.