P
Paavo Leinonen
Guest
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 neede din the XP cleint side).
In the performance monitor looks like nonpaged pool is 63.x 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.160.xxx.yyy. Switched 100/1000 mbits network.
How can I fix this?
-Paavo
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 neede din the XP cleint side).
In the performance monitor looks like nonpaged pool is 63.x 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.160.xxx.yyy. Switched 100/1000 mbits network.
How can I fix this?
-Paavo