network print as user not as guest

[ToddAndMargo]

Hi All,

I have a windows 2000 server that mounts WHFC Hylafax print shares
from
two W2k-Pro, sp4 computer and two XP-Pro, SP2 computers.

The two w2k-Pro shared WHFC printers work perfectly with the w2000
server.

The two XP machines complain that the "WHFC not running for user
Guest".
(The necessary "WHFC Monitor" is running as the current user.)

Is there a way to get XP-Pro to act the same way as w2k-Pro and
accept the network print job's credentials as the user (the same use
name
and password is being used on both sides)?

Many thanks,
-T

 

[Chuck]

Hi All,

I have a windows 2000 server that mounts WHFC Hylafax print shares
from
two W2k-Pro, sp4 computer and two XP-Pro, SP2 computers.

The two w2k-Pro shared WHFC printers work perfectly with the w2000
server.

The two XP machines complain that the "WHFC not running for user
Guest".
(The necessary "WHFC Monitor" is running as the current user.)

Is there a way to get XP-Pro to act the same way as w2k-Pro and
accept the network print job's credentials as the user (the same use
name
and password is being used on both sides)?

Many thanks,
-T

1) Disable Simple File Sharing.
2) Enable a non-Guest account with non-blank password.
3) Either a) Disable the Guest account on the server (and prepare to login
manually each time), or
b) Enable and Use the same non-Guest account on each client computer.
<http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#NonGuest>
http://nitecruzr.blogspot.com/2005/06/file-sharing-under-windows-xp.html#NonGuest

 

[ToddAndMargo]

1) Disable Simple File Sharing.

Did that

2) Enable a non-Guest account with non-blank password.

Did that too

3) Either a) Disable the Guest account on the server (and prepare to login
manually each time),

Didn't do that.

What do you mean "and prepare to login manually each time"? Everyone
already
has to sign in with their user name and password. I am confused.

or
b) Enable and Use the same non-Guest account on each client computer.

Did that.

Thank you for the link!

-T

 

[Chuck]

Did that


Did that too


Didn't do that.

What do you mean "and prepare to login manually each time"? Everyone
already
has to sign in with their user name and password. I am confused.



Did that.

Thank you for the link!

-T

T,

Windows XP Pro will setup a token for authentication with a given server,
similar to domain authentication, if you're using Advanced File Sharing. And,
if you selected "Reconnect at logon", it will keep that token for next time.

If the client and the server have a common non-Guest account activated for
network access, and if you're using that account from the client (having logged
in with that account / password), then you should authenticate to the server
automatically.

If you're having to login each time, to the server, when connecting thru the
network, then either the client is not running XP Pro, or one of them is not
running AFS. Or you're not using the right account from the client, with
matching password.

When you say

Everyone already has to sign in with their user name and password.

are you talking about logging in locally when starting a computer, or login to
the server, when connecting thru the network?

 

[ToddAndMargo]

Windows XP Pro will setup a token for authentication with a given server,
similar to domain authentication, if you're using Advanced File Sharing. And,
if you selected "Reconnect at logon", it will keep that token for next time.

If the client and the server have a common non-Guest account activated for
network access, and if you're using that account from the client (having logged
in with that account / password), then you should authenticate to the server
automatically.

It is. The problem is in the print driver.

If you're having to login each time, to the server, when connecting thru the
network, then either the client is not running XP Pro, or one of them is not
running AFS.

I thought that when I turned off simple file sharing, the AFS
automatically took over. Do I assume too much?

Or you're not using the right account from the client, with
matching password.

The other printers and file shares work just fine. The problem
is in the print driver.

When you say
are you talking about logging in locally when starting a computer, or login to
the server, when connecting thru the network?

I meant when they sit down at the w2k-server's console. I made sure
they had matching user names and passwords.

The problem with the WHFC print driver is that it runs a service
on the sharing computer under the current user's
user name. If the network client requests to print to it
under guest or any other user name, WHFC just pop up an error
message that guest or whoever is no running the service.
Ultimately WHFC needs to be fixed.

I will use your suggestion about turning off the client's
guest account. I will be out there this afternoon.

Thank you for the help.

-T

 

[ToddAndMargo]

Windows XP Pro will setup a token for authentication with a given server,
similar to domain authentication, if you're using Advanced File Sharing. And,
if you selected "Reconnect at logon", it will keep that token for next time.

If the client and the server have a common non-Guest account activated for
network access, and if you're using that account from the client (having logged
in with that account / password), then you should authenticate to the server
automatically.

It is. The problem is in the print driver.

If you're having to login each time, to the server, when connecting thru the
network, then either the client is not running XP Pro, or one of them is not
running AFS.

I thought that when I turned off simple file sharing, the AFS
automatically took over. Do I assume too much?

Or you're not using the right account from the client, with
matching password.

The other printers and file shares work just fine. The problem
is in the print driver.

When you say
are you talking about logging in locally when starting a computer, or login to
the server, when connecting thru the network?

I meant when they sit down at the w2k-server's console. I made sure
they had matching user names and passwords.

The problem with the WHFC print driver is that it runs a service
on the sharing computer under the current user's
user name. If the network client requests to print to it
under guest or any other user name, WHFC just pop up an error
message that guest or whoever is no running the service.
Ultimately WHFC needs to be fixed.

I will use your suggestion about turning off the client's
guest account. I will be out there this afternoon.

Thank you for the help.

-T