Re: XP Can't See Windows 2000 Server to Use Printer

From: LC (LC_at_discussions.microsoft.com)
Date: 09/10/04 

Date: Fri, 10 Sep 2004 05:43:04 -0700

Good Morning Chuck,

Everyone belongs to the same workgroup.

SFS was not disabled, but I disabled it by removing the check mark.
Local Security Policy for network access as already set to Classic.
I have set a non blank password for the "Guest" user on Latitude as well as
the Server, freedom.

Latitude still has an attitude--Can see any shares on Freedom. Can't link
to the printer.

You said that if you set Local Security Policy is set to "Guest Only" make
sure the Guess account is enabled, with a non blank pw. I'm not sure what
you mean here. I have the guest account enabled, but are you referring to a
particular policy under Security Options?

Thank you.

LC

"Chuck" wrote:

> On Thu, 9 Sep 2004 17:41:06 -0700, "LC" <LC@discussions.microsoft.com> wrote:
>
> >I have a mixed ethernet/wireless lan. All workstations have ethernet cards
> >and are hard coded with IP, DNS, etc (no DHCP). Two laptops have wireless
> >cards in addition to their ethernet lans. Everybody is running Windows 2000
> >except one XP laptop. One is a Windows 2000 server--not running active
> >directory, just as a workgroup.
> >
> >Everyone is happy except the XP laptop named Latitude. It has:
> >XP Professional
> >Wireless Card
> >Ethernet Port
> >XP SP2
> >I have disabled the ICS firewall
> >It is running computer browser as is everybody else
> >
> >I ran browstat:
> >
> >Status for domain LCSYS on transport
> >\Device\NetBT_Tcpip_{5F7FABF7-464E-4243-BACC-E4BCF6024852}
> > Browsing is active on domain.
> > Master browser name is: LATITUDE
> > Master browser is running build 2600
> > 1 backup servers retrieved from master LATITUDE
> > \\LATITUDE
> > There are 2 servers in domain LCSYS on transport
> >\Device\NetBT_Tcpip_{5F7FABF7-464E-4243-BACC-E4BCF6024852}
> > There are 1 domains in domain LCSYS on transport
> >\Device\NetBT_Tcpip_{5F7FABF7-464E-4243-BACC-E4BCF6024852}
> >
> >PROBLEM:
> >
> >I am trying to link to a printer on the Windows 2000 server and XP just
> >doesn't see it.
> >
> >XP can ping it by IP and netbios name (I have an LMHOSts) file.
> >
> >When I go out to the cmd line and type:
> >
> >net use lpt1: \\freedom\hp5 I receive System Error 66 has occurred. The
> >network resource type is not correct.
> >
> >When I do a new view \\freedom I receive the old System Error 53. I know
> >that means permissions. But the server freedom printer is set for everyone
> >to use. The guest accountn on the server is disabled.
>
> LC,
>
> Are all the computers in the same workgroup?
>
> On Latitude, check to see if Simple File Sharing (Control Panel - Folder Options
> - View - Advanced settings) is enabled or disabled. With XP Pro in a workgroup
> with Win2K, you'll need SFS disabled.
>
> With XP Pro, if SFS is disabled, check the Local Security Policy (Control Panel
> - Administrative Tools). Under Local Policies - Security Options, look at
> "Network access: Sharing and security model", and ensure it's set to "Classic -
> local users authenticate as themselves".
>
> With XP Pro, if you set the Local Security Policy to "Guest only", make sure
> that the Guest account is enabled, thru Local User Manager (Start - Run -
> "lusrmgr.msc"), and has an identical, non-blank, password on all computers. If
> "Classic", setup and use a common non-Guest account, with identical, non-blank,
> password on all computers.
>
> More about file sharing, between all different versions of Windows:
> <http://www.microsoft.com/downloads/details.aspx?FamilyID=87c0a6db-aef8-4bef-925e-7ac9be791028&DisplayLang=en>
>
> And about the Browser subsystem:
> <http://www.microsoft.com/technet/prodtechnol/winntas/deploy/prodspecs/ntbrowse.mspx>
>
> Cheers,
> Chuck
> Paranoia comes from experience - and is not necessarily a bad thing.
>

Relevant Pages

  • Re: Create public shared printer on XP Pro
    ... >>>an XP Pro computer so that users do not have to enter a user name and ... But you do need to enable either the Guest account on the ... >> printer server, or a common non-Guest account on each computer (including the ... >network" in Control Panel, Administrative Tools, Local Security Policy ...
    (microsoft.public.windowsxp.network_web)
  • Re: Remote Guest Account
    ... the local security policy prevents using blank passwords to connect via the network. ... Using the guest account is not a good idea, because everyone knows about it and thus it is programmed into automated attack programs. ... The account exists and is activated, but, it keeps saying access ...
    (microsoft.public.windows.terminal_services)
  • Re: Anonymous Acccess to File Share on Windows Server 2003
    ... First try giving the guest account a password. ... Local Security Policy configure the security option for limit ... local account use of blank password to console logon only to be disabled. ... Can they logon with credentials? ...
    (microsoft.public.windows.server.security)
  • Locking up the Desktop
    ... you could tweak the local security policy on ... the individual boxes if they are in a workgroup on in a ... GPO if they are part of an AD domain to prevent them from ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Create public shared printer on XP Pro
    ... I subsequently found that the Guest account was listed under, "Deny access to this computer from the network" in Control Panel, Administrative Tools, Local Security Policy under Local Policies, User Rights Assignment. ... But you do need to enable either the Guest account on the printer server, or a common non-Guest account on each computer. ...
    (microsoft.public.windowsxp.network_web)