very slow when clicked on network share

[Tony]

Sometimes, when i click on a network share, i get the hour glass for a while
before the files and folders show. why is that? the server is fast, fast
network, no users using server.

the client is xp and server is 2003

we are trying to migrate away from novell and novell mapped drives do not
have this latency

 

[Oli Restorick [MVP]]

How is DNS configured on your network? Can you provide example "ipconfig
/all" outputs from an affected workstation, your DCs and a machine
containing an affected network share?

Regards

Oli

 

[Lanwench [MVP - Exchange]]

Sometimes, when i click on a network share, i get the hour glass for
a while before the files and folders show. why is that? the server is
fast, fast network, no users using server.

the client is xp and server is 2003

we are trying to migrate away from novell and novell mapped drives do
not have this latency

Migrating from Novell to what - a Windows domain? If so, make sure your DNS
is set up right - that's the #1 cause of AD problems. All servers and
workstations should specify *only* the internal AD-integrated DNS server's
IP address in their network settings. The AD-integrated DNS server should be
set up with forwarders to your ISP's DNS servers for external resolution
and/or use root hints.

 

[Rick]

Sometimes, when i click on a network share, i get the hour glass for a while
before the files and folders show. why is that? the server is fast, fast
network, no users using server.

the client is xp and server is 2003

we are trying to migrate away from novell and novell mapped drives do not
have this latency

This is a known issue with certain versions of Novell's client.

See if this helps:

 

[Guest]

In Lanwench's reply, you mentioned "The AD-integrated DNS server should be
set up with forwarders to your ISP's DNS servers for external resolution
and/or use root hints."

I'm a DNS dummy and I'm a network admin running two Win2K servers--one as
the DC that controls user access to the Internet, user authentication, etc.
The other is an Exchange 2000 server.

On the DC, I have DNS running and root hints set up. I also have forwarder
to my Exchange 2000 Server, but not my ISP IP. Should I change this to the
ISP IP for the forwarder?

Thank you,

 

[Lanwench [MVP - Exchange]]

In Lanwench's reply, you mentioned "The AD-integrated DNS server
should be set up with forwarders to your ISP's DNS servers for
external resolution and/or use root hints."

I'm a DNS dummy and I'm a network admin running two Win2K
servers--one as the DC that controls user access to the Internet,
user authentication, etc. The other is an Exchange 2000 server.

On the DC, I have DNS running and root hints set up. I also have
forwarder to my Exchange 2000 Server, but not my ISP IP. Should I
change this to the ISP IP for the forwarder?

If you want. I would.