[prev in list] [next in list] [prev in thread] [next in thread] 

List:       nt-mgrs
Subject:    [nt-mgrs] SUMMARY: Printing through Windows 2000 DC without authenticating
From:       jonesey <jonesey () uoregon ! edu>
Date:       2003-04-16 22:11:33
[Download RAW message or body]

   Well, I gave up.  I had two suggestions:

1. Use TCP/IP printing instead.  I am unable to do this for 
complicated reasons.  It is also not quite as simple as 
point-and-print, which works really well.

2. If you can get Guest to work, people's computers should be able to 
cache the Domain\Guest username so that they won't have to enter it 
again.  Since Guest wasn't working, this wasn't an option.

   I ended up demoting the server back to a member server (using 
dcpromo) and enabling Guest locally.  It works like a champ now.  I 
plan to promote another server to be a DC so that I have a backup.

jonesey

Original message:
>   One of my Windows 2000 Server computers, my print server, is a 
>Domain Controller.  Until last week, it was a Member Server, which 
>meant it had its own  local user list.  I enabled Guest on this 
>local user list so that computers outside the domain could open the 
>server, see the print queues, set them up, and send print jobs to 
>the server without authenticating.  That worked.
>
>   When I promoted this server to be a Domain Controller, the local 
>user list went away.  Now it just has the Domain user list.
>
>   The problem: when computers outside of the domain try to connect 
>to the server or print, the print queues they have set up say 
>"Unable to Connect."  The workaround is to go to Start, choose Run, 
>type the name of the server, then enter a username and password to 
>authenticate against the domain.  This is what they had to do before 
>I enabled Guest locally when it was a Member Server.
>
>   I want people outside of the domain to be able to print to my 
>server's queues without authenticating.  I have tried to enable 
>Guest in the domain, and it says it's enabled (I know this is a Bad 
>Idea, but I don't have any better ones), but people still have to 
>authenticate before they are able to print.
>
>   If you're interested in what the server looks like, here are the 
>instructions to set up our print queues:
>
>http://aaa-output.uoregon.edu/oswinsetup/
>
>   Normally, step 4 can be skipped, but without Guest enabled, you 
>have to enter a username and password.
>
>   Any ideas?
>
>thanks
>jonesey
[prev in list] [next in list] [prev in thread] [next in thread]