Shared network resources cannot accessible after a while

We got a Win2003 DC and 30 XP Pros at office. Users share disks & printers.
But we have a weird problem, after a while (sometime 30 minutes, another time
1 hour, it's not clear, maybe never) users cannot access these resources (folders,
printers, etc) or access delayed.

For example you browse \\userPC\c$, when you click a folder, explorer window
freezes for a while (say 30 seconds) then the files listed at once. When you open
a file, Word freezes for a while, when you save, waits again and you look the hourglass.

When you try to print something it doesn't print, even you cannot examine printer properties.

I've discovered a way to fix this; closing user's (which has got problem / not the remote one's) session.
When you log-in again, everything comes back, now you may print or open what you want... For a while...



I've pinged and no problem. Overall, It's not TCP related problem. I can browse files thru Internet Explorer
at http://userPC/files (if there is a webserver) or I can connect remote machine via Remote Desktop. When
I got problem at browsing remote files (\\UserPC\c$) I open Remote Desktop to remote machine then browse
my own files (\\MyOwnPC\c$) there and I transfer files between remote and my machine without any trouble.


Sometime a password login box appears when I couldn't connect to \\UserPC\c$.
My pc should remember the user/pass but It asks me again and never accepts the pass
even I type the right pass. I type a different doman user/pass and say remember it.
Then everything is ok again, till login box appears next time. I switch user/pass on every turn.



These are 30 pc with different configs. Firewalls are disabled. Antivirus doesn't matter.
A new installed XP or old one no matter.


It looks like RPC related but I'm not sure and I don't know any way to diagnose the problem.
It's totally random thing. I have no clue, no reason...

Nime <(E-Mail Removed)> wrote:
> We got a Win2003 DC and 30 XP Pros at office. Users share disks &
> printers. But we have a weird problem, after a while (sometime 30 minutes,
> another time 1 hour, it's not clear, maybe never) users cannot
> access these resources (folders, printers, etc) or access delayed.
>
> For example you browse \\userPC\c$, when you click a folder, explorer
> window freezes for a while (say 30 seconds) then the files listed at once.
> When you open a file, Word freezes for a while, when you save, waits again
> and you
> look the hourglass.
> When you try to print something it doesn't print, even you cannot
> examine printer properties.
> I've discovered a way to fix this; closing user's (which has got
> problem / not the remote one's) session. When you log-in again,
> everything comes back, now you may print or open what you want... For
> a while...
>
>
> I've pinged and no problem. Overall, It's not TCP related problem. I
> can browse files thru Internet Explorer at http://userPC/files (if
> there is a webserver) or I can connect remote machine via Remote
> Desktop. When I got problem at browsing remote files (\\UserPC\c$) I open
> Remote
> Desktop to remote machine then browse my own files (\\MyOwnPC\c$) there
> and I transfer files between remote
> and my machine without any trouble.
>
> Sometime a password login box appears when I couldn't connect to
> \\UserPC\c$. My pc should remember the user/pass but It asks me again and
> never
> accepts the pass even I type the right pass. I type a different doman
> user/pass and
> say remember it. Then everything is ok again, till login box appears next
> time. I
> switch user/pass on every turn.
>
>
> These are 30 pc with different configs. Firewalls are disabled.
> Antivirus doesn't matter. A new installed XP or old one no matter.
>
>
> It looks like RPC related but I'm not sure and I don't know any way
> to diagnose the problem. It's totally random thing. I have no clue, no
> reason...

Maybe OT, but can I ask why you're sharing workstation resources when you've
got a domain and a server? You really ought to have *all* your data on the
server(s) and you should be using network printers you can share & manage at
the server. I would get rid of all local shares and clean this up - you've
got a very decentralized network right now and that really defeats the
purpose of having a server.

Nime wrote:
> We got a Win2003 DC and 30 XP Pros at office. Users share disks & printers.
> But we have a weird problem, after a while (sometime 30 minutes, another
> time
> 1 hour, it's not clear, maybe never) users cannot access these
> resources (folders,
> printers, etc) or access delayed.
>
> For example you browse \\userPC\c$, when you click a folder, explorer
> window
> freezes for a while (say 30 seconds) then the files listed at once. When
> you open a file, Word freezes for a while, when you save, waits again
> and you look the hourglass.
>
> When you try to print something it doesn't print, even you cannot
> examine printer properties.
>
> I've discovered a way to fix this; closing user's (which has got problem
> / not the remote one's) session. When you log-in again, everything comes
> back, now you may print or open what you want... For a while...
>
>
>
> I've pinged and no problem. Overall, It's not TCP related problem. I can
> browse files thru Internet Explorer
> at http://userPC/files (if there is a webserver) or I can connect remote
> machine via Remote Desktop. When I got problem at browsing remote files
> (\\UserPC\c$) I open Remote Desktop to remote machine then browse
> my own files (\\MyOwnPC\c$) there and I transfer files between remote
> and my machine without any trouble.
>
>
> Sometime a password login box appears when I couldn't connect to
> \\UserPC\c$.
> My pc should remember the user/pass but It asks me again and never
> accepts the pass
> even I type the right pass. I type a different doman user/pass and say
> remember it.
> Then everything is ok again, till login box appears next time. I switch
> user/pass on every turn.
>
>
>
> These are 30 pc with different configs. Firewalls are disabled.
> Antivirus doesn't matter.
> A new installed XP or old one no matter.
>
>
> It looks like RPC related but I'm not sure and I don't know any way to
> diagnose the problem.
> It's totally random thing. I have no clue, no reason...

There is a limit of 10 concurrent connections on an XP machine.
It may well be that you are exceeding that limit, and that closing a
user's session and then starting again is (just) giving you enough spare
connections.
I believe the default session timeout is 15 minutes.

Alister

I'm the admin and I browse every folder : )
Put webserver something, download and place a setup file
on user's desktop, etc.

OK I'm gonna simplify my question; imagine only shared printers.
Managers blame on me when they cannot print a page.




"Lanwench [MVP - Exchange]" <(E-Mail Removed) hoo.com>, iletide þunu yazdý
news:(E-Mail Removed)...

> Maybe OT, but can I ask why you're sharing workstation resources when you've got a domain and a server? You really ought to have
> *all* your data on the server(s) and you should be using network printers you can share & manage at the server. I would get rid of
> all local shares and clean this up - you've got a very decentralized network right now and that really defeats the purpose of
> having a server.
>

Maybe, but a manager does nothing on his laptop and he cannot print either : )
He only runs MSN Messenger, IE and opens a Word doc from shared folder
on domain controller. When he couldn't print something he calls me : ) or : (


May I increase that 10 limit? I think a registry setting could change it... I did it
for IE before...

--------------------------------------------------
From: "Alister" <(E-Mail Removed)>
Sent: Friday, April 17, 2009 3:41 PM
Newsgroups: microsoft.public.windows.server.networking
Subject: Re: Shared network resources cannot accessible after a while


> There is a limit of 10 concurrent connections on an XP machine.
> It may well be that you are exceeding that limit, and that closing a
> user's session and then starting again is (just) giving you enough spare
> connections.
> I believe the default session timeout is 15 minutes.
>
> Alister

Nime <(E-Mail Removed)> wrote:
> I'm the admin and I browse every folder : )

Why?

> Put webserver something, download and place a setup file
> on user's desktop, etc.

Why?
>
> OK I'm gonna simplify my question; imagine only shared printers.
> Managers blame on me when they cannot print a page.

I don't use shared printers on workstations, either. If a printer needs to
be used by multiple users, it is a networked printer and is shared from the
server.
>
>
>
>
> "Lanwench [MVP - Exchange]"
> <(E-Mail Removed) hoo.com>, iletide
> þunu yazdý news:(E-Mail Removed)...
>> Maybe OT, but can I ask why you're sharing workstation resources
>> when you've got a domain and a server? You really ought to have
>> *all* your data on the server(s) and you should be using network
>> printers you can share & manage at the server. I would get rid of
>> all local shares and clean this up - you've got a very decentralized
>> network right now and that really defeats the purpose of having a
>> server.

At least users map a folder as drive on DC. as Z:
Same problem occurs time after time. User logs off then logs on.
Not a comfortable solution, it's only annoying workout.



"Lanwench [MVP - Exchange]" <(E-Mail Removed) hoo.com>, iletide þunu yazdý
news:e50dM#(E-Mail Removed)...

I've checked, NET CONFIG SERVER and it displayed the sessions then I just remembered
I did set timeout value as 1 min to make server much responsive and it worked because
a dialog box never appeared which says "Maximum connections blah blah..."

In my case there is no more dialog box...


"Nime" <(E-Mail Removed)>, iletide þunu yazdý news:#XAcc$(E-Mail Removed)...
> Maybe, but a manager does nothing on his laptop and he cannot print either : )
> He only runs MSN Messenger, IE and opens a Word doc from shared folder
> on domain controller. When he couldn't print something he calls me : ) or : (
>
>
> May I increase that 10 limit? I think a registry setting could change it... I did it
> for IE before...
>
> --------------------------------------------------
> From: "Alister" <(E-Mail Removed)>
> Sent: Friday, April 17, 2009 3:41 PM
> Newsgroups: microsoft.public.windows.server.networking
> Subject: Re: Shared network resources cannot accessible after a while
>
>
>> There is a limit of 10 concurrent connections on an XP machine.
>> It may well be that you are exceeding that limit, and that closing a user's session and then starting again is (just) giving you
>> enough spare connections.
>> I believe the default session timeout is 15 minutes.
>>
>> Alister

Nime <(E-Mail Removed)> wrote:
> At least users map a folder as drive on DC. as Z:
> Same problem occurs time after time. User logs off then logs on.
> Not a comfortable solution, it's only annoying workout.

You haven't answered my questions. Stop sharing local resources. Use login
scripts to control drive mappings (and use /persistent:no if you use a batch
file with net use commands). It's really impossible to help you with the
information given and the setup you've got, I'm afraid.
>
>
>
> "Lanwench [MVP - Exchange]"
> <(E-Mail Removed) hoo.com>, iletide
> þunu yazdý news:e50dM#(E-Mail Removed)...

Nime <(E-Mail Removed)> wrote:
> I've checked, NET CONFIG SERVER and it displayed the sessions then I
> just remembered I did set timeout value as 1 min to make server much
> responsive and
> it worked because a dialog box never appeared which says "Maximum
> connections blah
> blah..."
> In my case there is no more dialog box...

Please see my reply. You're trying to put band-aids on what is a bad
configuration. Rather than wasting time on it, correct the setup so
everything is shared from the server and users have permissions only to what
they are supposed to access.
>
>
> "Nime" <(E-Mail Removed)>, iletide þunu yazdý
> news:#XAcc$(E-Mail Removed)...
>> Maybe, but a manager does nothing on his laptop and he cannot print
>> either : ) He only runs MSN Messenger, IE and opens a Word doc from
>> shared
>> folder on domain controller. When he couldn't print something he calls me
>> : ) or : ( May I increase that 10 limit? I think a registry
>> setting could
>> change it... I did it for IE before...
>>
>> --------------------------------------------------
>> From: "Alister" <(E-Mail Removed)>
>> Sent: Friday, April 17, 2009 3:41 PM
>> Newsgroups: microsoft.public.windows.server.networking
>> Subject: Re: Shared network resources cannot accessible after a while
>>
>>
>>> There is a limit of 10 concurrent connections on an XP machine.
>>> It may well be that you are exceeding that limit, and that closing
>>> a user's session and then starting again is (just) giving you
>>> enough spare connections. I believe the default session timeout is 15
>>> minutes.
>>>
>>> Alister