pesky network logon times

  • Thread starter Thread starter Trull
  • Start date Start date
T

Trull

Hello again,

Ok, ive searched almost every google result on this subject and i think im
so close to success, but im not quite there!


I have several workstations running various OS's connected to a NAT
router/switch which shares the internet.
Also on the network is a Win2k3 Active Directory Domain Controller.

I just reinstalled 2k3 because i'd messed up the dns settings, and currently
running on the server is AD and a File Server.

I also reinstalled 2k on one of the workstations.

When i first logged in it when fine, but now ive done something again which
makes it wait ages after entering your password and ages on the "loading
personal settings" bit.

Ive tried forcing Kerberos to use TCP but that didnt help.

Most replies to similar questions say that its DNS and to make sure it
points to my server, but i dont want it to do that, i dont need my server to
be a DNS server (or do i - my NAT router shares my Internet so i didnt think
i needed this?).

here is the output of an ipconfig /all on my 2k machine:


========================================================
Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : mainpc
Primary DNS Suffix . . . . . . . : XXX.no-ip.com
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : XXX.no-ip.com
no-ip.com
Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : PCI 10/100 Fast Ethernet Adapter(983)
Physical Address. . . . . . . . . : 00-0B-2B-0B-EE-XX
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.254 << ROUTER
DHCP Server . . . . . . . . . . . : 192.168.0.254 << ROUTER
DNS Servers . . . . . . . . . . . : 194.168.8.100 << ISP
194.168.4.100 << ISP
Lease Obtained. . . . . . . . . . : 17 November 2003 23:20:48
Lease Expires . . . . . . . . . . : 29 December 2003 15:20:48
=========================================================

All i can think that i did to 'break' it was make a group policy for uses to
remap their my documents to a network location. i disabled this after the
fault appeared but it didnt solve it. Deleting it didnt fix it, or making a
new user to log in as :s


What can i do to find out what the problem is? Is it local or server based?

Would really appreciate some help with this its driving me crazy!

Oh yeah, also, the few times it did logon correctly, it didnt run my logon
scripts, which did run manually. This related?

Cheers guys

Andrew Bullock
 
Ipconfig should all point to your server. How many nics in your server? You
should have DNS-server only listen to the server-IP and put the
ISP-DNS-numbers in tab Forwarders.
Got options 003, 006 and 015 in DHCP-server, Scope options?

Marina
 
Only one NIC in the server, as i said, it doesnt need to function as a DNS
server as my router deals with the internet.

Do i absolutely need to make my workstations retrieve DNS through the
server? will that fix the waiting problem?

If so, what exactly do i need to do? Ill read some tuts i suppose.

If i dont absolutely need to enable DNS to fix this waiting problem what
else can i do?

The reason im against reconfiguring the DNS is because the server is down
quite a bit and that would mean people cant access the internet whilst its
down :S

Or can i somehow put my server as the primary DNS server, but the ISP as a
backup in the workstations DNS lists?


Cheers
Andrew
 
Hi Andrew,

W2K-server is much happier if it runs DNS-server, so yes install it and
configure it.
It will absolutely fix your logon problems.
Your server won't be down but might need a reboot if DNS hasn't been
installed yet.
You configure it that it should listen to your server-IP only. The
ISP-DNS-numbers should be put in tab Forwarders.
Options 003, 006 and 015 should be set in DHCP-server, Scope options.
Clients should be set to obtain an IP and DNS automatically from your
DNS-server.
DNS on the servernic should *only* point to your server-IP.

marina
 
Thanks alot it works now

Andrew

Marina Roos said:
Hi Andrew,

W2K-server is much happier if it runs DNS-server, so yes install it and
configure it.
It will absolutely fix your logon problems.
Your server won't be down but might need a reboot if DNS hasn't been
installed yet.
You configure it that it should listen to your server-IP only. The
ISP-DNS-numbers should be put in tab Forwarders.
Options 003, 006 and 015 should be set in DHCP-server, Scope options.
Clients should be set to obtain an IP and DNS automatically from your
DNS-server.
DNS on the servernic should *only* point to your server-IP.

marina
Click to expand...
 
Back
Top