XP Clients require password to connect to shared printers on 2003 Server

Daniel Farst

Hi,

As part of our transition away from a SAMBA based domain to a
workgroup we are setting up a new print/file server running Server
2003 R2. This server is a fresh install which has never before been
connected to the domain controller and our client computers are
running on cached credentials as I am one-by-one moving them to the
new workgroup. The server setup went smoothly and all the printers are
working fine from the server, however when an XP client (domain or
workgroup) tries to connect to the printer through the server it is
requiring server logon credentials.

Since we are moving away from a domain authenticated login to a local
login I can't see adding all the user accounts to the server. Ideally
the server would just accept any account for access to the printers,
however I cannot seem to get 2k3 to do this. I've tried activating the
guest account and adding guest to the printer ACLs but nothing seems
to work.

I'm not worried about security as the firewall restricts access to
everything but the local subnet and the server is only running
printing.

My understanding is that it is actually the IPC$ share that is
requiring the password and that since this is connecting before the
individual shares this is why I can't connect.

Does anyone have any ideas on how I can get around this?

Thanks!
-- Dan

Daniel Farst

On Jun 16, 9:50 am, "Kerry Brown" <k...@kdbNOSPAMsys-tems.c*a*m>
wrote:
> "Daniel Farst" <> wrote in message
>
> news:1181969005.416683.35250@k79g2000hse.googlegro ups.com...
>
>
>
> > Hi,
>
> > As part of our transition away from a SAMBA based domain to a
> > workgroup we are setting up a new print/file server running Server
> > 2003 R2. This server is a fresh install which has never before been
> > connected to the domain controller and our client computers are
> > running on cached credentials as I am one-by-one moving them to the
> > new workgroup. The server setup went smoothly and all the printers are
> > working fine from the server, however when an XP client (domain or
> > workgroup) tries to connect to the printer through the server it is
> > requiring server logon credentials.
>
> > Since we are moving away from a domain authenticated login to a local
> > login I can't see adding all the user accounts to the server. Ideally
> > the server would just accept any account for access to the printers,
> > however I cannot seem to get 2k3 to do this. I've tried activating the
> > guest account and adding guest to the printer ACLs but nothing seems
> > to work.
>
> > I'm not worried about security as the firewall restricts access to
> > everything but the local subnet and the server is only running
> > printing.
>
> > My understanding is that it is actually the IPC$ share that is
> > requiring the password and that since this is connecting before the
> > individual shares this is why I can't connect.
>
> > Does anyone have any ideas on how I can get around this?
>
> Yes, don't go backwards from a domain based network to a workgroup. One of
> the major advantages of a domain is the ability to use a single logon to
> access domain resources. In a workgroup all the servers will need to have
> all the accounts setup locally on the each server. If someone changes their
> password you have to change it on every computer that has a shared resource.
>
> --
> Kerry Brown
> Microsoft MVP - Shell/Userhttp://www.vistahelp.ca

Unfortunatly that decision has already been made and I have no control
over it. In the mean time, I set up an XP machine to run as a print
server. It is performing exactly as I want it to, allowing connections
to any user to use the printers, so obviously this is a configuration
issue with the 2k3 server. Is this something that has been locked out
of 2k3? Or is it buried somewhere in the local security policy that I
haven't found yet?

-- Dan

Kerry Brown

"Daniel Farst" <> wrote in message
news:1181969005.416683.35250@k79g2000hse.googlegro ups.com...
> Hi,
>
> As part of our transition away from a SAMBA based domain to a
> workgroup we are setting up a new print/file server running Server
> 2003 R2. This server is a fresh install which has never before been
> connected to the domain controller and our client computers are
> running on cached credentials as I am one-by-one moving them to the
> new workgroup. The server setup went smoothly and all the printers are
> working fine from the server, however when an XP client (domain or
> workgroup) tries to connect to the printer through the server it is
> requiring server logon credentials.
>
> Since we are moving away from a domain authenticated login to a local
> login I can't see adding all the user accounts to the server. Ideally
> the server would just accept any account for access to the printers,
> however I cannot seem to get 2k3 to do this. I've tried activating the
> guest account and adding guest to the printer ACLs but nothing seems
> to work.
>
> I'm not worried about security as the firewall restricts access to
> everything but the local subnet and the server is only running
> printing.
>
> My understanding is that it is actually the IPC$ share that is
> requiring the password and that since this is connecting before the
> individual shares this is why I can't connect.
>
> Does anyone have any ideas on how I can get around this?
>


Yes, don't go backwards from a domain based network to a workgroup. One of
the major advantages of a domain is the ability to use a single logon to
access domain resources. In a workgroup all the servers will need to have
all the accounts setup locally on the each server. If someone changes their
password you have to change it on every computer that has a shared resource.

--
Kerry Brown
Microsoft MVP - Shell/User

Kerry Brown

"Daniel Farst" <> wrote in message
news:1182025168.510567.314160@q75g2000hsh.googlegr oups.com...
> On Jun 16, 9:50 am, "Kerry Brown" <k...@kdbNOSPAMsys-tems.c*a*m>
> wrote:
>> "Daniel Farst" <> wrote in message
>>
>> news:1181969005.416683.35250@k79g2000hse.googlegro ups.com...
>>
>>
>>
>> > Hi,
>>
>> > As part of our transition away from a SAMBA based domain to a
>> > workgroup we are setting up a new print/file server running Server
>> > 2003 R2. This server is a fresh install which has never before been
>> > connected to the domain controller and our client computers are
>> > running on cached credentials as I am one-by-one moving them to the
>> > new workgroup. The server setup went smoothly and all the printers are
>> > working fine from the server, however when an XP client (domain or
>> > workgroup) tries to connect to the printer through the server it is
>> > requiring server logon credentials.
>>
>> > Since we are moving away from a domain authenticated login to a local
>> > login I can't see adding all the user accounts to the server. Ideally
>> > the server would just accept any account for access to the printers,
>> > however I cannot seem to get 2k3 to do this. I've tried activating the
>> > guest account and adding guest to the printer ACLs but nothing seems
>> > to work.
>>
>> > I'm not worried about security as the firewall restricts access to
>> > everything but the local subnet and the server is only running
>> > printing.
>>
>> > My understanding is that it is actually the IPC$ share that is
>> > requiring the password and that since this is connecting before the
>> > individual shares this is why I can't connect.
>>
>> > Does anyone have any ideas on how I can get around this?
>>
>> Yes, don't go backwards from a domain based network to a workgroup. One
>> of
>> the major advantages of a domain is the ability to use a single logon to
>> access domain resources. In a workgroup all the servers will need to have
>> all the accounts setup locally on the each server. If someone changes
>> their
>> password you have to change it on every computer that has a shared
>> resource.
>>
>> --
>> Kerry Brown
>> Microsoft MVP - Shell/Userhttp://www.vistahelp.ca
>
> Unfortunatly that decision has already been made and I have no control
> over it. In the mean time, I set up an XP machine to run as a print
> server. It is performing exactly as I want it to, allowing connections
> to any user to use the printers, so obviously this is a configuration
> issue with the 2k3 server. Is this something that has been locked out
> of 2k3? Or is it buried somewhere in the local security policy that I
> haven't found yet?
>
> -- Dan
>


Is the XP print server Pro or Home. If it's Pro is simple file sharing
turned on? Are XP clients Pro or Home? XP Home will share printers without
authentication. XP Pro with simple file sharing on works the same. They use
the guest account. Because of the security implications I've never tried to
setup simple file sharing on a server if it even exists. Maybe someone else
will know the answer. I do know it will work if you create all the accounts
and passwords on the server.

--
Kerry Brown
Microsoft MVP - Shell/User

Kerry Brown

"Daniel Farst" <> wrote in message
news:1182025168.510567.314160@q75g2000hsh.googlegr oups.com...
> On Jun 16, 9:50 am, "Kerry Brown" <k...@kdbNOSPAMsys-tems.c*a*m>
> wrote:
>> "Daniel Farst" <> wrote in message
>>
>> news:1181969005.416683.35250@k79g2000hse.googlegro ups.com...
>>
>>
>>
>> > Hi,
>>
>> > As part of our transition away from a SAMBA based domain to a
>> > workgroup we are setting up a new print/file server running Server
>> > 2003 R2. This server is a fresh install which has never before been
>> > connected to the domain controller and our client computers are
>> > running on cached credentials as I am one-by-one moving them to the
>> > new workgroup. The server setup went smoothly and all the printers are
>> > working fine from the server, however when an XP client (domain or
>> > workgroup) tries to connect to the printer through the server it is
>> > requiring server logon credentials.
>>
>> > Since we are moving away from a domain authenticated login to a local
>> > login I can't see adding all the user accounts to the server. Ideally
>> > the server would just accept any account for access to the printers,
>> > however I cannot seem to get 2k3 to do this. I've tried activating the
>> > guest account and adding guest to the printer ACLs but nothing seems
>> > to work.
>>
>> > I'm not worried about security as the firewall restricts access to
>> > everything but the local subnet and the server is only running
>> > printing.
>>
>> > My understanding is that it is actually the IPC$ share that is
>> > requiring the password and that since this is connecting before the
>> > individual shares this is why I can't connect.
>>
>> > Does anyone have any ideas on how I can get around this?
>>
>> Yes, don't go backwards from a domain based network to a workgroup. One
>> of
>> the major advantages of a domain is the ability to use a single logon to
>> access domain resources. In a workgroup all the servers will need to have
>> all the accounts setup locally on the each server. If someone changes
>> their
>> password you have to change it on every computer that has a shared
>> resource.
>>
>> --
>> Kerry Brown
>> Microsoft MVP - Shell/Userhttp://www.vistahelp.ca
>
> Unfortunatly that decision has already been made and I have no control
> over it. In the mean time, I set up an XP machine to run as a print
> server. It is performing exactly as I want it to, allowing connections
> to any user to use the printers, so obviously this is a configuration
> issue with the 2k3 server. Is this something that has been locked out
> of 2k3? Or is it buried somewhere in the local security policy that I
> haven't found yet?
>


Have you tried adding the Everyone group?

--
Kerry Brown
Microsoft MVP - Shell/User

Daniel Farst

On Jun 16, 9:50 am, "Kerry Brown" <k...@kdbNOSPAMsys-tems.c*a*m>
wrote:
> "Daniel Farst" <> wrote in message
>
> news:1181969005.416683.35250@k79g2000hse.googlegro ups.com...
>
>
>
> > Hi,
>
> > As part of our transition away from a SAMBA based domain to a
> > workgroup we are setting up a new print/file server running Server
> > 2003 R2. This server is a fresh install which has never before been
> > connected to the domain controller and our client computers are
> > running on cached credentials as I am one-by-one moving them to the
> > new workgroup. The server setup went smoothly and all the printers are
> > working fine from the server, however when an XP client (domain or
> > workgroup) tries to connect to the printer through the server it is
> > requiring server logon credentials.
>
> > Since we are moving away from a domain authenticated login to a local
> > login I can't see adding all the user accounts to the server. Ideally
> > the server would just accept any account for access to the printers,
> > however I cannot seem to get 2k3 to do this. I've tried activating the
> > guest account and adding guest to the printer ACLs but nothing seems
> > to work.
>
> > I'm not worried about security as the firewall restricts access to
> > everything but the local subnet and the server is only running
> > printing.
>
> > My understanding is that it is actually the IPC$ share that is
> > requiring the password and that since this is connecting before the
> > individual shares this is why I can't connect.
>
> > Does anyone have any ideas on how I can get around this?
>
> Yes, don't go backwards from a domain based network to a workgroup. One of
> the major advantages of a domain is the ability to use a single logon to
> access domain resources. In a workgroup all the servers will need to have
> all the accounts setup locally on the each server. If someone changes their
> password you have to change it on every computer that has a shared resource.
>
> --
> Kerry Brown
> Microsoft MVP - Shell/Userhttp://www.vistahelp.ca

Unfortunatly that decision has already been made and I have no control
over it. In the mean time, I set up an XP machine to run as a print
server. It is performing exactly as I want it to, allowing connections
to any user to use the printers, so obviously this is a configuration
issue with the 2k3 server. Is this something that has been locked out
of 2k3? Or is it buried somewhere in the local security policy that I
haven't found yet?

-- Dan

Kerry Brown

"Daniel Farst" <> wrote in message
news:1182025168.510567.314160@q75g2000hsh.googlegr oups.com...
> On Jun 16, 9:50 am, "Kerry Brown" <k...@kdbNOSPAMsys-tems.c*a*m>
> wrote:
>> "Daniel Farst" <> wrote in message
>>
>> news:1181969005.416683.35250@k79g2000hse.googlegro ups.com...
>>
>>
>>
>> > Hi,
>>
>> > As part of our transition away from a SAMBA based domain to a
>> > workgroup we are setting up a new print/file server running Server
>> > 2003 R2. This server is a fresh install which has never before been
>> > connected to the domain controller and our client computers are
>> > running on cached credentials as I am one-by-one moving them to the
>> > new workgroup. The server setup went smoothly and all the printers are
>> > working fine from the server, however when an XP client (domain or
>> > workgroup) tries to connect to the printer through the server it is
>> > requiring server logon credentials.
>>
>> > Since we are moving away from a domain authenticated login to a local
>> > login I can't see adding all the user accounts to the server. Ideally
>> > the server would just accept any account for access to the printers,
>> > however I cannot seem to get 2k3 to do this. I've tried activating the
>> > guest account and adding guest to the printer ACLs but nothing seems
>> > to work.
>>
>> > I'm not worried about security as the firewall restricts access to
>> > everything but the local subnet and the server is only running
>> > printing.
>>
>> > My understanding is that it is actually the IPC$ share that is
>> > requiring the password and that since this is connecting before the
>> > individual shares this is why I can't connect.
>>
>> > Does anyone have any ideas on how I can get around this?
>>
>> Yes, don't go backwards from a domain based network to a workgroup. One
>> of
>> the major advantages of a domain is the ability to use a single logon to
>> access domain resources. In a workgroup all the servers will need to have
>> all the accounts setup locally on the each server. If someone changes
>> their
>> password you have to change it on every computer that has a shared
>> resource.
>>
>> --
>> Kerry Brown
>> Microsoft MVP - Shell/Userhttp://www.vistahelp.ca
>
> Unfortunatly that decision has already been made and I have no control
> over it. In the mean time, I set up an XP machine to run as a print
> server. It is performing exactly as I want it to, allowing connections
> to any user to use the printers, so obviously this is a configuration
> issue with the 2k3 server. Is this something that has been locked out
> of 2k3? Or is it buried somewhere in the local security policy that I
> haven't found yet?
>
> -- Dan
>


Is the XP print server Pro or Home. If it's Pro is simple file sharing
turned on? Are XP clients Pro or Home? XP Home will share printers without
authentication. XP Pro with simple file sharing on works the same. They use
the guest account. Because of the security implications I've never tried to
setup simple file sharing on a server if it even exists. Maybe someone else
will know the answer. I do know it will work if you create all the accounts
and passwords on the server.

--
Kerry Brown
Microsoft MVP - Shell/User

Kerry Brown

"Daniel Farst" <> wrote in message
news:1182025168.510567.314160@q75g2000hsh.googlegr oups.com...
> On Jun 16, 9:50 am, "Kerry Brown" <k...@kdbNOSPAMsys-tems.c*a*m>
> wrote:
>> "Daniel Farst" <> wrote in message
>>
>> news:1181969005.416683.35250@k79g2000hse.googlegro ups.com...
>>
>>
>>
>> > Hi,
>>
>> > As part of our transition away from a SAMBA based domain to a
>> > workgroup we are setting up a new print/file server running Server
>> > 2003 R2. This server is a fresh install which has never before been
>> > connected to the domain controller and our client computers are
>> > running on cached credentials as I am one-by-one moving them to the
>> > new workgroup. The server setup went smoothly and all the printers are
>> > working fine from the server, however when an XP client (domain or
>> > workgroup) tries to connect to the printer through the server it is
>> > requiring server logon credentials.
>>
>> > Since we are moving away from a domain authenticated login to a local
>> > login I can't see adding all the user accounts to the server. Ideally
>> > the server would just accept any account for access to the printers,
>> > however I cannot seem to get 2k3 to do this. I've tried activating the
>> > guest account and adding guest to the printer ACLs but nothing seems
>> > to work.
>>
>> > I'm not worried about security as the firewall restricts access to
>> > everything but the local subnet and the server is only running
>> > printing.
>>
>> > My understanding is that it is actually the IPC$ share that is
>> > requiring the password and that since this is connecting before the
>> > individual shares this is why I can't connect.
>>
>> > Does anyone have any ideas on how I can get around this?
>>
>> Yes, don't go backwards from a domain based network to a workgroup. One
>> of
>> the major advantages of a domain is the ability to use a single logon to
>> access domain resources. In a workgroup all the servers will need to have
>> all the accounts setup locally on the each server. If someone changes
>> their
>> password you have to change it on every computer that has a shared
>> resource.
>>
>> --
>> Kerry Brown
>> Microsoft MVP - Shell/Userhttp://www.vistahelp.ca
>
> Unfortunatly that decision has already been made and I have no control
> over it. In the mean time, I set up an XP machine to run as a print
> server. It is performing exactly as I want it to, allowing connections
> to any user to use the printers, so obviously this is a configuration
> issue with the 2k3 server. Is this something that has been locked out
> of 2k3? Or is it buried somewhere in the local security policy that I
> haven't found yet?
>


Have you tried adding the Everyone group?

--
Kerry Brown
Microsoft MVP - Shell/User

daniel.farst@gmail.com

On Jun 16, 5:00 pm, "Kerry Brown" <k...@kdbNOSPAMsys-tems.c*a*m>
wrote:
> "Daniel Farst" <> wrote in message
>
> news:1182025168.510567.314160@q75g2000hsh.googlegr oups.com...
>
>
>
> > On Jun 16, 9:50 am, "Kerry Brown" <k...@kdbNOSPAMsys-tems.c*a*m>
> > wrote:
> >> "Daniel Farst" <> wrote in message
>
> >>news:1181969005.416683.35250@k79g2000hse.googleg roups.com...
>
> >> > Hi,
>
> >> > As part of our transition away from a SAMBA based domain to a
> >> > workgroup we are setting up a new print/file server running Server
> >> > 2003 R2. This server is a fresh install which has never before been
> >> > connected to the domain controller and our client computers are
> >> > running on cached credentials as I am one-by-one moving them to the
> >> > new workgroup. The server setup went smoothly and all the printers are
> >> > working fine from the server, however when an XP client (domain or
> >> > workgroup) tries to connect to the printer through the server it is
> >> > requiring server logon credentials.
>
> >> > Since we are moving away from a domain authenticated login to a local
> >> > login I can't see adding all the user accounts to the server. Ideally
> >> > the server would just accept any account for access to the printers,
> >> > however I cannot seem to get 2k3 to do this. I've tried activating the
> >> > guest account and adding guest to the printer ACLs but nothing seems
> >> > to work.
>
> >> > I'm not worried about security as the firewall restricts access to
> >> > everything but the local subnet and the server is only running
> >> > printing.
>
> >> > My understanding is that it is actually the IPC$ share that is
> >> > requiring the password and that since this is connecting before the
> >> > individual shares this is why I can't connect.
>
> >> > Does anyone have any ideas on how I can get around this?
>
> >> Yes, don't go backwards from a domain based network to a workgroup. One
> >> of
> >> the major advantages of a domain is the ability to use a single logon to
> >> access domain resources. In a workgroup all the servers will need to have
> >> all the accounts setup locally on the each server. If someone changes
> >> their
> >> password you have to change it on every computer that has a shared
> >> resource.
>
> >> --
> >> Kerry Brown
> >> Microsoft MVP - Shell/Userhttp://www.vistahelp.ca
>
> > Unfortunatly that decision has already been made and I have no control
> > over it. In the mean time, I set up an XP machine to run as a print
> > server. It is performing exactly as I want it to, allowing connections
> > to any user to use the printers, so obviously this is a configuration
> > issue with the 2k3 server. Is this something that has been locked out
> > of 2k3? Or is it buried somewhere in the local security policy that I
> > haven't found yet?
>
> Have you tried adding the Everyone group?
>
> --
> Kerry Brown
> Microsoft MVP - Shell/Userhttp://www.vistahelp.ca

The XP server is pro currently running simple file sharing, however I
have used XP servers before and even with SFS turned off printer
connections don't require passwords unless you remove the everyone
user from the ACL.

On the 2003 server I have added the Everyone group, the Anonymous
Logon user, the guest user, and the Guests group, as well as using the
local security policy editor to give anonymous users everyone
privileges. I'm officially stumped.

Security wise, the server is running a good firewall, only allowing
inbound connections from the local subnet, and the institution's DHCP
policy quarantines all non-registered computers in a separate VLAN,
preventing access to the secure network (i.e. you can't just walk up
and plug-in a random computer and access the network). I realize it's
not actually secure, but it's just a print server and the worst it can
cost me is paper/toner and printer downtime which compared to
continuing to run our 10-year old SAMBA based DC is still an
improvement. The file server is linux based and is not set to trust
the print server.

Another weird thing I came across: When setting up the XP server, I
used the same printer share names, hostname and static IP as the old
server in an attempt to make the switch as transparent as possible for
the users. The clients, previously referring to the server using the
fully qualified domain name(\\Hostname.Subnet.case.edu\PrinterShare
style), refused to connect to the printers on the XP server even
though everything else was identical. I manually deleted the old
printers, and scoured the registry for references to the old server
and the printer installation still failed with an error of "Printer
does not exist" even with printers that were not previously installed
on the system. This was solved by installing the printers using just
the smb hostname (\\Hostname\PrinterShare style). Any Ideas?

-- Dan

daniel.farst@gmail.com

On Jun 16, 5:00 pm, "Kerry Brown" <k...@kdbNOSPAMsys-tems.c*a*m>
wrote:
> "Daniel Farst" <> wrote in message
>
> news:1182025168.510567.314160@q75g2000hsh.googlegr oups.com...
>
>
>
> > On Jun 16, 9:50 am, "Kerry Brown" <k...@kdbNOSPAMsys-tems.c*a*m>
> > wrote:
> >> "Daniel Farst" <> wrote in message
>
> >>news:1181969005.416683.35250@k79g2000hse.googleg roups.com...
>
> >> > Hi,
>
> >> > As part of our transition away from a SAMBA based domain to a
> >> > workgroup we are setting up a new print/file server running Server
> >> > 2003 R2. This server is a fresh install which has never before been
> >> > connected to the domain controller and our client computers are
> >> > running on cached credentials as I am one-by-one moving them to the
> >> > new workgroup. The server setup went smoothly and all the printers are
> >> > working fine from the server, however when an XP client (domain or
> >> > workgroup) tries to connect to the printer through the server it is
> >> > requiring server logon credentials.
>
> >> > Since we are moving away from a domain authenticated login to a local
> >> > login I can't see adding all the user accounts to the server. Ideally
> >> > the server would just accept any account for access to the printers,
> >> > however I cannot seem to get 2k3 to do this. I've tried activating the
> >> > guest account and adding guest to the printer ACLs but nothing seems
> >> > to work.
>
> >> > I'm not worried about security as the firewall restricts access to
> >> > everything but the local subnet and the server is only running
> >> > printing.
>
> >> > My understanding is that it is actually the IPC$ share that is
> >> > requiring the password and that since this is connecting before the
> >> > individual shares this is why I can't connect.
>
> >> > Does anyone have any ideas on how I can get around this?
>
> >> Yes, don't go backwards from a domain based network to a workgroup. One
> >> of
> >> the major advantages of a domain is the ability to use a single logon to
> >> access domain resources. In a workgroup all the servers will need to have
> >> all the accounts setup locally on the each server. If someone changes
> >> their
> >> password you have to change it on every computer that has a shared
> >> resource.
>
> >> --
> >> Kerry Brown
> >> Microsoft MVP - Shell/Userhttp://www.vistahelp.ca
>
> > Unfortunatly that decision has already been made and I have no control
> > over it. In the mean time, I set up an XP machine to run as a print
> > server. It is performing exactly as I want it to, allowing connections
> > to any user to use the printers, so obviously this is a configuration
> > issue with the 2k3 server. Is this something that has been locked out
> > of 2k3? Or is it buried somewhere in the local security policy that I
> > haven't found yet?
>
> Have you tried adding the Everyone group?
>
> --
> Kerry Brown
> Microsoft MVP - Shell/Userhttp://www.vistahelp.ca

The XP server is pro currently running simple file sharing, however I
have used XP servers before and even with SFS turned off printer
connections don't require passwords unless you remove the everyone
user from the ACL.

On the 2003 server I have added the Everyone group, the Anonymous
Logon user, the guest user, and the Guests group, as well as using the
local security policy editor to give anonymous users everyone
privileges. I'm officially stumped.

Security wise, the server is running a good firewall, only allowing
inbound connections from the local subnet, and the institution's DHCP
policy quarantines all non-registered computers in a separate VLAN,
preventing access to the secure network (i.e. you can't just walk up
and plug-in a random computer and access the network). I realize it's
not actually secure, but it's just a print server and the worst it can
cost me is paper/toner and printer downtime which compared to
continuing to run our 10-year old SAMBA based DC is still an
improvement. The file server is linux based and is not set to trust
the print server.

Another weird thing I came across: When setting up the XP server, I
used the same printer share names, hostname and static IP as the old
server in an attempt to make the switch as transparent as possible for
the users. The clients, previously referring to the server using the
fully qualified domain name(\\Hostname.Subnet.case.edu\PrinterShare
style), refused to connect to the printers on the XP server even
though everything else was identical. I manually deleted the old
printers, and scoured the registry for references to the old server
and the printer installation still failed with an error of "Printer
does not exist" even with printers that were not previously installed
on the system. This was solved by installing the printers using just
the smb hostname (\\Hostname\PrinterShare style). Any Ideas?

-- Dan