Re: Network drives - slow initial access

I'm glad you've finally narrowed it down. IIRC, the Novell client used IPX
protocol but will run on TCP/IP. Can you uncheck the IPX protocol after
you've installed the client?


Another thing may be to check the bindings on the NIC and make sure that
TCP/IP is listed first.

--
Merv Porter [SBS-MVP]
============================

"Michael" <Michael@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:24BE8FD8-1F7E-410F-A69E-4CB713948B2D@xxxxxxxxxxxxxxxx
I think I've finally found the problem... Novell client. Uninstalled this
as
we no longer use it in house but still use it for other sites and bam,
I've
not had a single problem since. I do, unfortunately, have to reinstall it
though :(
To think of all the settings I've changed on the server in the last month!

"Michael" wrote:

Hi Merv
I checked the IsDomainMaster setting in the registry and it was indeed
set
to FALSE.
MaintainServerList was already set to Yes.
I've checked a few other SBS boxes and they seem to have the same
settings :(
I've now set IDM to TRUE. All workstations appear to be set to 'Auto'.
Whether its worth settings this to false I don't know, yet. I will try
changing the server side setting first and see how we go.
Thanks again.

"Merv Porter [SBS-MVP]" wrote:

Hi Michael,

After reading your orignal post, I see that you did the
"autodisconnect"
thing.

Could you please post an ipconfig /all for the server and for a
workstation. I presume all profiles on all workstations are
experiencing
this problem.

Also, what happens if you now create a new user with the same mapping?
And does this happen if an admin logs onto a workstation, maps the
drives,
waits and then tries to access the mapped drives?
Is your antivirus on the server or the workstations set up to scan
"network"
drives?
What happens if you delete and then re-create the mapped drives on a
workstation?
No roaming profiles, right?

Another thought...

Maybe make the server the "Master Browser" for the network (may require
a
reboot of the server and/or workstations)

Control Network Browser Elections
http://www.winguides.com/registry/display.php/54/

Set IsDomainMaster from FALSE to TRUE
MaintainServerList to YES

Make sure the workstation settings are not set to IsDomainMaster = TRUE

--
Merv Porter [SBS-MVP]
============================

"Michael" <Michael@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:04F34088-94BF-4084-A13A-E9CC4B4B02BD@xxxxxxxxxxxxxxxx
Hi Merv
I had already set autodisconnect and oplocks before making my initial
post.
No change.

"Merv Porter [SBS-MVP]" wrote:

Same thing (autodisconnect), but for Windows 2003...

Mapped Drive Connection to Network Share May Be Lost
http://support.microsoft.com/kb/297684

--
Merv Porter [SBS-MVP]
============================

"Merv Porter [SBS-MVP]" <mwport@xxxxxxxxxxxxxxxxxxx> wrote in
message
news:e2WtAc99GHA.3860@xxxxxxxxxxxxxxxxxxxxxxx
I don't think the NIC is at fault here.

On the server, try setting autodisconnect to "never":

How Autodisconnect Works in Windows NT and Windows 2000
http://support.microsoft.com/kb/138365

From a command prompt:

net config server /autodisconnect:-1

--
Merv Porter [SBS-MVP]
============================

"Michael" <Michael@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3E31A77D-FFAA-4926-ADC5-BD1671AA7FC5@xxxxxxxxxxxxxxxx
No joy I'm afraid.
I noticed the server also does not have an option to do 1000/full
(Gb
card).
Could this be something to do with permissions? Perhaps it's
taking
(hugely)
longer than normal to check the ACL or something...

"Merv Porter [SBS-MVP]" wrote:

Try setting the NIC on the server and the workstation(s) NIC to
Full
duplex,
100 MB and not autodetect. If this is how each NIC is now set,
then
try
setting all NICs to autodetetect.

--
Merv Porter [SBS-MVP]
============================

"Michael" <Michael@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:7CFEA5E8-99E6-4E12-A951-86ABD374672A@xxxxxxxxxxxxxxxx
OK. I was very hopeful with this setting but unfortunately it
was
not
the
cause of our problem. Any other ideas? :)
Thanks

"Michael" wrote:

Thanks for the quick reply too, much appreciated.
Merv! I specifically remember checking this on the client
PC's but
overlooked it on the server.
It was indeed enabled! Now disabled, fingers crossed!


"Merv Porter [SBS-MVP]" wrote:

Just a guess... on the SBS server NIC, do you have Power
Management
set
to:
"Allow the computer to turn off this device to save power"?

(rt. click) Network Adapter | Properties | Configure |
Power
Management
|
(uncheck) "Allow the computer to turn off this device to
save
power"

Same for the workstation. Also for the workstation, in
Control
Panel |
Power Options, turn off Hibernation and set the hard drives
to
never
turn
off.

May be more places to look...

Slow login, network browsing on SBS 2003
http://groups.google.com/group/microsoft.public.windows.server.sbs/browse_thread/thread/523983126722666c/7f1c4c944fcbe0e8?lnk=st&q=sbs+2003+slow+network+access&rnum=3&hl=en#7f1c4c944fcbe0e8

--
Merv Porter [SBS-MWP]
============================

"Michael" <Michael@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:6117F85C-6379-42AC-BE07-C97BBE84E8E0@xxxxxxxxxxxxxxxx
Hi!
We seem to be having this issue on our SBS2003 STD SP1
box.
Basically,
after
a period of inactivity, trying to access the mapped
drives in
My
Computer
takes approx 14 seconds from double clicking to actually
opening.
The
same
kind of time is also noted when opening a Word document
off
the
server...
always after a period of inactivity. I can replicate this
problem
on
more
than one machine.

I have disabled autodisconnect on the server and oplocks;
this
has
made no
discernible difference. I have even gone as far as
disabling
auto
disconnect
on two client machines too (XP Pro, SP2) but the same
behaviour
is
observed
and it is highly frustrating. All clients are DHCP'd from
the
SBS
box; DNS
points only at the server.

Server has one NIC, a Broadcom NetXtreme Gigabit. IP is
static
and
DNS has
one entry (itself).
Thanks for any pointers.
















.

Relevant Pages

  • Re: Daily Server Report (Critical Errors, Event ID: 537)
    ... Does this issue happen on client workstation or server? ... Does your server and all clients' workstation work well now? ... issue in your Network? ...
    (microsoft.public.windows.server.sbs)
  • Re: IE 6 and Proxy Setting Exceptions
    ... searched on the TechNet DVD for this "Internal Client Concepts in ISA Server ... 2006" and I was able to get an understanding for the key, and value settings. ... ProgramName.EXE Disable/DisableEx 1 ...
    (microsoft.public.isa)
  • Re: WSUS Client not yet reported
    ... The client still fails to report. ... Check your server status ... Suggestion 2: Check the IIS settings: ... any updates in your thread. ...
    (microsoft.public.windows.server.sbs)
  • RE: Unable to ping client2
    ... I understand that the server box can not ping one ... client workstation after upgraded to SBS 2003 SP1. ... Reboot the SBS Server. ... On the client workstation, run "ipconfig /release" and then run ...
    (microsoft.public.windows.server.sbs)
  • Re: RWW-RDP
    ... It utilizes a cross-over cable between it and the SBS Server. ... Ehternet from hub to server and from hub to workstation ... Ethernet adapter Server Local Area Connection: ... Also, Merv, I can connect to the server and client machines on the ...
    (microsoft.public.windows.server.sbs)
Loading