Hi All, our organisation has a Win 2003 domain. We have a couple of
associates who work in the office that need to connect to a printer on
our network. They have their own laptops running XP Home, but they
will not be member of our domain.

I attempted to connect them to the printer by browsing to the printer.
it prompted me for a username and password, which I supplied (I set up
an account on the server for them, just so that they could
authenticate). However, it wouldnt let me install the printer.
Perhaps I needed to be an administrator to install a printer on a users
machine (anyone know??) No problem, I just used the administrator
account to install the printer.

The installation worked fine, and they could print alright, until they
logged out or rebooted the machine. After that, whenever they printed
they would get Access Denied errors. Now, if I deleted and reinstalled
the printers as administrator, it would work again, but obviously this
is not an option. So, essentially, my question is: Is there anyway to
allow these users to access a printer on the network (like they did
above) and keep the settings on reboot? and using their accounts
rather than administrator (which I'm guessing is a stupid security
risk).

Try creating a local port on an XP Pro machine. Then, get the XP Home
machines to point to that XP Pro machine - should work (as ACLs are less
strict)


<(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi All, our organisation has a Win 2003 domain. We have a couple of
> associates who work in the office that need to connect to a printer on
> our network. They have their own laptops running XP Home, but they
> will not be member of our domain.
>
> I attempted to connect them to the printer by browsing to the printer.
> it prompted me for a username and password, which I supplied (I set up
> an account on the server for them, just so that they could
> authenticate). However, it wouldnt let me install the printer.
> Perhaps I needed to be an administrator to install a printer on a users
> machine (anyone know??) No problem, I just used the administrator
> account to install the printer.
>
> The installation worked fine, and they could print alright, until they
> logged out or rebooted the machine. After that, whenever they printed
> they would get Access Denied errors. Now, if I deleted and reinstalled
> the printers as administrator, it would work again, but obviously this
> is not an option. So, essentially, my question is: Is there anyway to
> allow these users to access a printer on the network (like they did
> above) and keep the settings on reboot? and using their accounts
> rather than administrator (which I'm guessing is a stupid security
> risk).
>

[Dexter Mahadeo]

Did you try using a UPN "(E-Mail Removed)" when connecting to the printer remotely with these guys' workgroup accounts?

Dexter Mahadeo
Trinidad

Originally Posted by (E-Mail Removed)

Hi All, our organisation has a Win 2003 domain. We have a couple of
associates who work in the office that need to connect to a printer on
our network. They have their own laptops running XP Home, but they
will not be member of our domain.

I attempted to connect them to the printer by browsing to the printer.
it prompted me for a username and password, which I supplied (I set up
an account on the server for them, just so that they could
authenticate). However, it wouldnt let me install the printer.
Perhaps I needed to be an administrator to install a printer on a users
machine (anyone know??) No problem, I just used the administrator
account to install the printer.

The installation worked fine, and they could print alright, until they
logged out or rebooted the machine. After that, whenever they printed
they would get Access Denied errors. Now, if I deleted and reinstalled
the printers as administrator, it would work again, but obviously this
is not an option. So, essentially, my question is: Is there anyway to
allow these users to access a printer on the network (like they did
above) and keep the settings on reboot? and using their accounts
rather than administrator (which I'm guessing is a stupid security
risk).