workstations can't see mapped drives on network

[Guest]

quickly;
1. have Win2K server, XP Pro desktops.
2. They all sign into the server no problem.
3. Each computer's hdd is shared and each computer is mapped to each hdd

My dilema
1. Some XP Pro machines take almost 8-10 mins to log onto the win2k server.
2. Some XP Pro machines can't see some mapped drives.

These issues occurr on a few machines. The balance of the network is just
fine.

 

[Phillip Windell]

quickly;
1. have Win2K server, XP Pro desktops.
2. They all sign into the server no problem.
3. Each computer's hdd is shared and each computer is mapped to each hdd

Forget "mapped drives",...those went away along with rubbing two sticks
together to start a fire. Use normal UNC Network pathes,...you can use
Shortcuts with them to make it more convenient.

My dilema
1. Some XP Pro machines take almost 8-10 mins to log onto the win2k server.
2. Some XP Pro machines can't see some mapped drives.

1.Turn off the Windows Firewall.
2. Make all machines (*all*, even the DC itself) use the DC you are
logging
into as the DNS Server (the *only* DNS server). The DC/DNS machine
then uses the ISP's DNS in the Forwarders List in the DNS Server
Configuration.
3. Never use two Nics in any machine unless it is serving as a Firewall
Device
or a LAN Router.


--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/techinfo/Guidance/2004.asp
http://www.microsoft.com/isaserver/techinfo/Guidance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp

Deployment Guidelines for ISA Server 2004 Enterprise Edition
http://www.microsoft.com/technet/prodtechnol/isa/2004/deploy/dgisaserver.mspx
-----------------------------------------------------

 

[Kurt]

And remember Active Directory REQUIRES a working local DNS. Long logons are
almost always improperly confiigured DNS servers or clients.

....kurt