Unable to Access Printer on WinME system

[BBear]

I have two systems both connected to a simple hub (that is also
connected to a highspeed modem). The first system (Sys-A) is running
WinME, the second system (Sys-B)is a laptop running Win2K. I have a
printer connected to the parallel port on sys-a. I want to print from
sys-b to the printer attached to sys-a. I've tried almost everything.

sys-a is using share-level access and the "primary netowrk logon" is
"client for MS networks". I have a user on sys-a created to be the
same name as the user on sys-b which I log into via a cached version of
the domain login. I have set the workgroup on sys-a to match that of
the domain on sys-b. (BTW - I have little or no flexibility to change
sys-b; however I should not that once I did an experiment and changed
sys-b to be a workgroup instead of a domain, and matched the two and it
worked, except in that mode I cannot use sys-b for it's normal intended
purposes.) I've also disabled the firewall on sys-a with no change in
results.

I have enable Print sharing on the sys-a printer, and it is indeed
shared. I installed NetBUI protocol, cause I read in a post somewhere
that it solved other similar problems - not mine.

What works:
On sys-b, a Net View reveals BOTH sys-b, and sys-a names correctly. I
can ping AND tracert sys-a from sys-b no problem.


What doesn't work:
A run sys-a command gives the error: "sys-a is not accessible; there
are currnetly no logon servers available to service the logon request".
When I do a Net View \\sys-a (from sys-b) I get: "System error 5 ;
access is denied."
When I try to add printer as a network printer, it simply doesn't find
it, although it does see sys-a. I did add a local port however and
called it \\sys-a\printer and that takes, but when I try to do a test
print, it will not print and generates the error: "test print failed,
unable to create a print job." If I try to print to that local port
from an application it says "you do not have persmission to access that
printer".

Any ideas?

 

[Brian Oakes [MSFT]]

Since you are logged into the domain, you will try and seek a DC for your
authentication provider.

When you get the Access is denied error, that tell you that your connection
is ok, but the username/password you are connecting as isn't.

So make sure on the WinME system on the printer and shares you don't have
any restrictions.

--

Brian Oakes

This posting is provided "AS IS" with no warranties and confers no rights.
Please reply to the newsgroup so that others may benefit.

 

[Guest]

Thanks Brian for the info, it does help to solidify a few things I was
wondering about. BTW I am having the same problem with printers and
files shares.

I did verify, the printer and shares have no passwords or other
restrictions that I can find.

In WinME , is there a restriction on the user password length? Must I
be logged into WinME with the same User/Password as on Win2K or how does
the WinME system learn about the Win2K logon - is it by system or user
or system/user or domain/login or login, etc?

Thanks.

 

[Brian Oakes [MSFT]]

What happens in normal circumstances is when a like username/password is
presented this is considered to be transitive credentials. So this is why in
workgroup scenarios we always say use a like username/password.

Normally it would be by domain\username or machine\username but not for
Windows9x and Me. It would just be username.

Either way, the security on ME really wasn't existent. So as long as you
have full control listed on the shares you should be ok.
--

Brian Oakes

This posting is provided "AS IS" with no warranties and confers no rights.
Please reply to the newsgroup so that others may benefit.