Mapped network connection dropped

We have a printer which is shared from the windows 2003 server through
network drive Z:
There are 5 Computers who have Domain user accounts who are getting this
error message.

"An error occured while reconnecting Z to \\server\public\shared
Microsft network: Local device name is already in use. Connection has not
been restored"

2 other computers who don`t use domain user accounts to log into the server
have no problem connecting to printer over the network.

ran gpresults
after running GPresult this was part of file.
COMPUTER SETTINGS
------------------
CN=SERVER,OU=Domain Controllers,DC=server01,DC=futuretechwest
Last time Group Policy was applied: at 9:25:16 AM
Group Policy was applied from: server.server01.futuretechwest
Group Policy slow link threshold: 500 kbps
Domain Name: SERVER01
Domain Type: Windows 2000

Applied Group Policy Objects
-----------------------------
Default Domain Controllers Policy
Default Domain Policy
FTW Staff

The following GPOs were not applied because they were filtered out
-------------------------------------------------------------------
Local Group Policy
Filtering: Not Applied (Empty)

The computer is a part of the following security groups
-------------------------------------------------------
BUILTIN\Administrators
Everyone
BUILTIN\Users
BUILTIN\Pre-Windows 2000 Compatible Access
Windows Authorization Access Group
NT AUTHORITY\NETWORK
NT AUTHORITY\Authenticated Users
This Organization
SERVER$
Domain Controllers
NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS
--
Griff

hemsky83 wrote:
> I have tried that as well but it still disconnects. The only difference I
> can find so far is that the computers with the problem are using a static IP
> address and the ones that arent having any issues have dynamic.
> But I can`t see how it would matter can you?
> Thanks
> --
> Griff


So, you're sharing a printer through an NTFS folder share? Why not
just share the printer normally? I'm assuming the printer in question
is just sitting out there on it's own network port. Even if it's
locally attached to the server (via USB or parallel port), you can
still share it out through the server's printer options in the Control
Panel.

I'm not sure why the connections are dropping out. If your printer
and/or server are using DHCP, that could be why (if you don't have DHCP
reservations set up for them). You really should try running all
static addresses, or all DHCP addresses if possible. But I think your
solution here is to properly share out the printer.