windows logon to network

Posted: 12-10-2003, 12:22 AM
Windows profile logon to the network it takes a long time
for your desktop items to appear. You do not receive an
error message.
Reply With Quote

Responses to "windows logon to network"

Nictu
Guest
Posts: n/a
 
windows logon to network
Posted: 12-10-2003, 01:01 AM
You havent given alot of info but check and see if you are
using the servers ip address for in the DNS.
>-----Original Message-----
>Windows profile logon to the network it takes a long time
>for your desktop items to appear. You do not receive an
>error message.
>.
>
Reply With Quote
Ron Lowe
Guest
Posts: n/a
 
Re: windows logon to network
Posted: 12-10-2003, 07:26 PM
"nuch@yahoo.com" <anonymous@discussions.microsoft.com> wrote in message
news:03d801c3beb3$b82c4bc0$a501280a@phx.gbl...
> Windows profile logon to the network it takes a long time
> for your desktop items to appear. You do not receive an
> error message.

Not much info to go on, but DNS is a common isue.
Check this before looking at anything else.

Here's my usual checklist for DNS:

XP differs from previous versions of windows in that it uses
DNS as it's primary name resolution method for finding domain
controllers:

How Domain Controllers Are Located in Windows XP
http://support.microsoft.com/default...b;en-us;314861

If DNS is misconfigured, XP will spend a lot of time waiting for it to
timeout before it tries using legacy NT4 sytle NetBIOS.
( Which may or may not work. )

1) Ensure that the XP clients are all configured to point to the local
DNS server which hosts the AD domain. That will probably be the
win2k server itself.
They should NOT be pointing an an ISP's DNS server.
An 'ipconfig /all' on the XP box should reveal ONLY the domain's
DNS server.

( you should use the DHCP server to push out the local DNS server
address. )

2) Ensure DNS server on win2k is configured to permit dynamic updates.

3) Ensure the win2k server points to itself as a DNS server.

4) For external ( internet ) name resolution, specify your ISP's DNS server
not on the clients, but in the 'forwarders' tab of the local win2k DNS
server.

On the DNS server, if you cannot access the 'Forwarders' and 'Root Hints'
tabs because they are greyed out, that is because there is a root zone (".")
present on the DNS server. You MUST delete this root zone to permit the
server to forward unresolved queries to yout ISP or the root servers.
Accept any nags etc, and let it delete any corresponding reverse lookuop
zones if it asks.


The following articles may assist you in setting up DNS correctly:

Setting Up the Domain Name System for Active Directory
http://support.microsoft.com/default...b;en-us;237675
HOW TO: Configure DNS for Internet Access in Windows 2000
http://support.microsoft.com/default...b;en-us;300202


--
Best Regards,
Ron Lowe
MS-MVP Windows Networking


Reply With Quote
 
LinkBack Thread Tools Display Modes
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
Network Logon Dan G Russ Windows Vista Networking & Sharing 3 01-06-2007 08:29 PM
network logon?? Gregory Burgh Windows XP Network & Web 1 11-11-2003 11:40 PM
Network logon Vernon Windows XP Network & Web 1 10-23-2003 01:29 AM
XP home network logon onto NT4 network Tony Windows XP Network & Web 0 09-13-2003 11:26 AM
Slow Network Logon on NT 4.0 Network Robert Vorwaller Windows XP Network & Web 1 07-09-2003 08:08 PM


1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90