Hi,

I have Vista Ultimate 64-bit computer as a server for home network. The
clients are mixed Vista (Ultimate) 64-bit and XP (Professional) 32-bit
computers.

After installing Vista SP1 the Vista server reliability has gone bad for XP
clients.

When I use one of the Vista server disk shares from XP client heavily, the
connection does down and I get "Not enough server storage is available to
process this command" and/or "System error 58" in the client side.

Vista server event viewer shows these error messages soon after the problems:

- The server was unable to allocate from the system nonpaged pool because
the pool was empty (system log / source srv / event ID 2019)

- The server was unable to allocate from the system nonpaged pool because
the server reached the configured limit for nonpaged pool allocations (system
log / source srv / event ID 2017)

- The server was unable to allocate a work item 43419 times in the last 60
seconds (system log / source srv / event ID 2021) - this is a warning only

The funny thing is that I can continue to use the same disk share from Vista
client, but to be able to use the server again from the XP client I need to
reboot the Vista server (no actions needed in the XP client side).

In the performance monitor looks like nonpaged pool is sixty something
megabytes, and only like 10% allocated. However, I have not done any tunings
or adjustments to the server or client systems, I think the swap file set-up
is about the only relevant thing, and all computers ave "enough" permanent
swap (several gigabytes for the XP computers, something like 12-16 gigabytes
for the Vista server and client).

XP clients have 2GB of RAM, Vista computers have 4GB (both client and server).

Local IP addresses in use, 192.168.xxx.yyy. Switched 100/1000 mbits network.

How can I fix this?

-Paavo

Did you check out the links Meinolf Weber posted to your thread in another
newsgroup?

--
Kerry Brown
MS-MVP - Windows Desktop Experience: Systems Administration
http://www.vistahelp.ca/phpBB2/



"Paavo Leinonen" wrote in message
...
Hi,

I have Vista Ultimate 64-bit computer as a server for home network. The
clients are mixed Vista (Ultimate) 64-bit and XP (Professional) 32-bit
computers.

After installing Vista SP1 the Vista server reliability has gone bad for
XP
clients.

When I use one of the Vista server disk shares from XP client heavily, the
connection does down and I get "Not enough server storage is available to
process this command" and/or "System error 58" in the client side.

Vista server event viewer shows these error messages soon after the
problems:

- The server was unable to allocate from the system nonpaged pool because
the pool was empty (system log / source srv / event ID 2019)

- The server was unable to allocate from the system nonpaged pool because
the server reached the configured limit for nonpaged pool allocations
(system
log / source srv / event ID 2017)

- The server was unable to allocate a work item 43419 times in the last 60
seconds (system log / source srv / event ID 2021) - this is a warning
only

The funny thing is that I can continue to use the same disk share from
Vista
client, but to be able to use the server again from the XP client I need
to
reboot the Vista server (no actions needed in the XP client side).

In the performance monitor looks like nonpaged pool is sixty something
megabytes, and only like 10% allocated. However, I have not done any
tunings
or adjustments to the server or client systems, I think the swap file
set-up
is about the only relevant thing, and all computers ave "enough" permanent
swap (several gigabytes for the XP computers, something like 12-16
gigabytes
for the Vista server and client).

XP clients have 2GB of RAM, Vista computers have 4GB (both client and
server).

Local IP addresses in use, 192.168.xxx.yyy. Switched 100/1000 mbits
network.

How can I fix this?

-Paavo

Hi,

I did, I was going to update this after a few more tests but here is the
current situation.

MaxMpxCt is now 100 (default 10), MaxWorkItems is now 512 (default 64), and
the Size is now 2 (default was 1). These are located in
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Lanmanserver\Parameters.
Adjusting there parameters did not change the Vista server behaviour at all.

I also tried adjusting NonPagedPoolSize to 40000000hex (default was 0) in
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Session Manager\Memory
Management, but this did not help either.

The other links were also good but did not help me to solve this problem.

Anything else I can try? This feels a litttle bit stupid, quad-core 4GB
computer with 64-bit Vista Ultimate cannot serve single XP client doing heavy
disk operations over 100mbits local area connection. And this is about the
only problem there is, all the computers and the home network is operating
very nicely.

But the problem is very easy to repeat: reboot the server, start copying
10000+ little pictures (filesize ~10-200kB, resolution less than 1k*1k
pixels) from the XP client disk to the Vista server disk, and in a minute or
so the server dies to the XP client, all commands fail (dir z:, net use, net
view, etc.). But the Vista server continues to server another (Vista 64-bit)
client.

SHould I adjust Lanmanserver/Parameters Size to 3? The Vista server was not
used otherwise, then the XP client used the disk, to there was no other load
for it.

-Paavo

"Kerry Brown" wrote:

Did you check out the links Meinolf Weber posted to your thread in another
newsgroup?

--
Kerry Brown
MS-MVP - Windows Desktop Experience: Systems Administration
http://www.vistahelp.ca/phpBB2/



"Paavo Leinonen" wrote in message
...
Hi,

I have Vista Ultimate 64-bit computer as a server for home network. The
clients are mixed Vista (Ultimate) 64-bit and XP (Professional) 32-bit
computers.

After installing Vista SP1 the Vista server reliability has gone bad for
XP
clients.

When I use one of the Vista server disk shares from XP client heavily, the
connection does down and I get "Not enough server storage is available to
process this command" and/or "System error 58" in the client side.

Vista server event viewer shows these error messages soon after the
problems:

- The server was unable to allocate from the system nonpaged pool because
the pool was empty (system log / source srv / event ID 2019)

- The server was unable to allocate from the system nonpaged pool because
the server reached the configured limit for nonpaged pool allocations
(system
log / source srv / event ID 2017)

- The server was unable to allocate a work item 43419 times in the last 60
seconds (system log / source srv / event ID 2021) - this is a warning
only

The funny thing is that I can continue to use the same disk share from
Vista
client, but to be able to use the server again from the XP client I need
to
reboot the Vista server (no actions needed in the XP client side).

In the performance monitor looks like nonpaged pool is sixty something
megabytes, and only like 10% allocated. However, I have not done any
tunings
or adjustments to the server or client systems, I think the swap file
set-up
is about the only relevant thing, and all computers ave "enough" permanent
swap (several gigabytes for the XP computers, something like 12-16
gigabytes
for the Vista server and client).

XP clients have 2GB of RAM, Vista computers have 4GB (both client and
server).

Local IP addresses in use, 192.168.xxx.yyy. Switched 100/1000 mbits
network.

How can I fix this?

-Paavo

You should post this to the original thread. It is good manners to respond
to someone who tried to help you. There are other questions that need to be
asked to continue trouble shooting but it would be best to keep to the
original thread so that people searching for similar problems will see the
full thread. The way it is now no one can follow through all the trouble
shooting steps.

--
Kerry Brown
MS-MVP - Windows Desktop Experience: Systems Administration
http://www.vistahelp.ca/phpBB2/



"Paavo Leinonen" wrote in message
...
Hi,

I did, I was going to update this after a few more tests but here is the
current situation.

MaxMpxCt is now 100 (default 10), MaxWorkItems is now 512 (default 64),
and
the Size is now 2 (default was 1). These are located in
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Lanmanserver\Parameters.
Adjusting there parameters did not change the Vista server behaviour at
all.

I also tried adjusting NonPagedPoolSize to 40000000hex (default was 0) in
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Session Manager\Memory
Management, but this did not help either.

The other links were also good but did not help me to solve this problem.

Anything else I can try? This feels a litttle bit stupid, quad-core 4GB
computer with 64-bit Vista Ultimate cannot serve single XP client doing
heavy
disk operations over 100mbits local area connection. And this is about the
only problem there is, all the computers and the home network is operating
very nicely.

But the problem is very easy to repeat: reboot the server, start copying
10000+ little pictures (filesize ~10-200kB, resolution less than 1k*1k
pixels) from the XP client disk to the Vista server disk, and in a minute
or
so the server dies to the XP client, all commands fail (dir z:, net use,
net
view, etc.). But the Vista server continues to server another (Vista
64-bit)
client.

SHould I adjust Lanmanserver/Parameters Size to 3? The Vista server was
not
used otherwise, then the XP client used the disk, to there was no other
load
for it.

-Paavo

"Kerry Brown" wrote:

Did you check out the links Meinolf Weber posted to your thread in
another
newsgroup?

--
Kerry Brown
MS-MVP - Windows Desktop Experience: Systems Administration
http://www.vistahelp.ca/phpBB2/



"Paavo Leinonen" wrote in
message
...
Hi,

I have Vista Ultimate 64-bit computer as a server for home network. The
clients are mixed Vista (Ultimate) 64-bit and XP (Professional) 32-bit
computers.

After installing Vista SP1 the Vista server reliability has gone bad
for
XP
clients.

When I use one of the Vista server disk shares from XP client heavily,
the
connection does down and I get "Not enough server storage is available
to
process this command" and/or "System error 58" in the client side.

Vista server event viewer shows these error messages soon after the
problems:

- The server was unable to allocate from the system nonpaged pool
because
the pool was empty (system log / source srv / event ID 2019)

- The server was unable to allocate from the system nonpaged pool
because
the server reached the configured limit for nonpaged pool allocations
(system
log / source srv / event ID 2017)

- The server was unable to allocate a work item 43419 times in the last
60
seconds (system log / source srv / event ID 2021) - this is a warning
only

The funny thing is that I can continue to use the same disk share from
Vista
client, but to be able to use the server again from the XP client I
need
to
reboot the Vista server (no actions needed in the XP client side).

In the performance monitor looks like nonpaged pool is sixty something
megabytes, and only like 10% allocated. However, I have not done any
tunings
or adjustments to the server or client systems, I think the swap file
set-up
is about the only relevant thing, and all computers ave "enough"
permanent
swap (several gigabytes for the XP computers, something like 12-16
gigabytes
for the Vista server and client).

XP clients have 2GB of RAM, Vista computers have 4GB (both client and
server).

Local IP addresses in use, 192.168.xxx.yyy. Switched 100/1000 mbits
network.

How can I fix this?

-Paavo

We've been fighting this problem since around the end of February (see
http://forums.microsoft.com/TechNet/...315&SiteID=17).
I even have a support case open with Microsoft. As usual recently, they're
clueless and really don't seem to have the ability to solve these problems.

This is an annoying and time wasting problem if you have shares on a Vista
platform in a network containing XP clients. It occurs with both x86 & x64
Vista systems. It's not only XP clients that have problems, it's XP-like
clients that have problems as well (i.e., Windows Server 2003). The Vista
Service Pack did not fix it. As a matter of fact, my feeling is a hotfix
caused the problem because it suddenly appeared.

I have several serious problems with Vista that I did not have with XP. If
I didn't have to develop applications for Vista, I would use XP all the time.