Network Logon From Win2K to WinME

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Given this scenario, I think the problem comes down to logging onto
Win2K as a Domain/Login and then logging onto WinME as a workgroup. I
cannot change (I can, but that's not the setup I need) the Win2K system.
What else can I do so that I can connection from Win2K to ME files and
printers?


--------------------------
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?
 
On Sys-B, when you get to the logon screen, click the Options button and
select the local machine instead of the domain. If you cannot logon this
way, log back onto the domain with cached credentials and try to create a
local user account with administrator privileges - then logon to the local
machine using that account. Also, you may have to install Win2k drivers for
the WinME printer.

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
 
Thanks Doug. Yes, I can access the printer IF I login to the local
machine (Sys-B) with common workgroups, instead of the domain.
However, I need to be able to access the printer/files while logged into
the domain. So I'm still stuck. I'm beginning to think that this might
be impossible. Thanks.
 
1. Depends on why you 'need' to be logged onto the domain - you may be able
to make files/resources/whatever available to your local machine account; or

2. Try this: On Sys-B create a local printer (clear the automatically
detect my printer box) on LPT1 - same make and model as Sys-A. At a command
prompt enter:

net use lpt1 \\Sys-A\<printersharename> <password> /user:<workgroupname>
\<username>

You may have to experiment with syntax - See:

http://www.microsoft.com/technet/tr...dowsserver2003/proddocs/entserver/net_use.asp

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
 
Back
Top