win98 cant access win2k under simple workgroup
Results 1 to 9 of 9

Thread: win98 cant access win2k under simple workgroup

  1. #1
    Registered User
    Join Date
    Apr 2001
    Location
    dallas, tx
    Posts
    29

    Post win98 cant access win2k under simple workgroup

    ive got 2 pcs. 1 98 and 1 2k. theyre going through a hub and they can see each other,
    but when 98 tries to access 2k. it cant do
    it. ive tried creating an account for it,
    etc. im stumped. it still isnt able to grab
    files from it. there not on a domain. ive got netbeui and file/printer sharing on both
    and same workgroup. 2k can grab stuff from 98 fine, its just the other way around that dont work. what steps am i missing? 98 is on windows logon, not client for ms networks. ill try that i guess. i dont know. im just learning 2k and its far superior than any other ms windows that ive used, but i just want 98 to grab files from it. please assist.
    thanks.
    steve in dallas

  2. #2
    Registered User ShadowKing's Avatar
    Join Date
    Dec 1999
    Location
    WA
    Posts
    743

    Post

    You need to either enable the guest account or create a user on the Win2k box that has the same name as the user logging onto the Win98 box.
    Matt

    "If you have been tempted into evil, fly from it. It is not falling into the water, but lying in it, that drowns"

  3. #3
    Registered User
    Join Date
    May 2001
    Location
    New Orleans
    Posts
    290

    Post

    Yes, but you notice he said that he *had* created a user on the Win2K machine and that didn't work.

    The reason is that although you created an account for the Win98 user on the Win2000 machine, Win98 cannot log into the network unless you are using "Client for Microsoft Networks" as your primary logon. The name says it all. That protocol enables you to act as a client in a workgroup or domain situation (well, really any network I guess), while "Microsoft Family Logon" was only designed to keep seperate profiles for users (desktop, color scheme, screensaver, etc.).

    You will also want to double-check that the Win98 user is listed among the users granted "Access this computer from the network" permission in Local Security Policy.
    Community standards do not maintain themselves: They're
    maintained by people actively applying them, visibly, in public. - Eric Raymond

  4. #4
    Registered User
    Join Date
    Apr 2001
    Location
    dallas, tx
    Posts
    29

    Post

    okay great. thanks. but one problem remains.
    the 98 box can access the 2k box, but it
    still wont see my shared folders for actually
    accessing. i changed the primary net logon to client for ms networks and then created
    the user on 2k... and it logins fine now, but
    the 98 machine still wont see the actual shared folders on 2k. i hope this makes sense. please reply.
    steve in dallas

  5. #5
    Registered User
    Join Date
    May 2001
    Location
    New Orleans
    Posts
    290

    Post

    Well, have you changed any Local Security Policies? If you change the default anonymous access permission from "None. Rely on default permissions" to "Do not enumerate SAM and shares" then you will not see the shares in Network Neighborhood, but you still have access to them. This option disables browsing shared folders for all users irregardless of whether it is an anonymous login or not. To check if this is the case, go to Start->Run on the Win98 box and type in the location of one of the Win2K shares, such as:
    \\{win2kbox}\{sharedfolder}

    If an explorer window pops open with that directory, then you need to double check your security permissions in Win2K with Local Security Policy if you've changed anything.

    If you get an error message instead, then you need to double check your TCP/IP settings and make sure they are all correct as this can also occur if TCP/IP is incorrectly configured. (The computer name showing up in Network Neighborhood is actually done by NetBIOS, not TCP/IP, so if the computer is shown, but you cannot connect, this is usually indicative of incorrect TCP/IP settings)

    As a matter of fact, you mentioned that you had installed IPX/SPX and File and Printer Sharing. But you did not say that you had TCP/IP installed. Microsoft File and Printer Sharing for Microsoft Networks will not work without TCP/IP. IPX/SPX is a novell protocol most commonly used for playing games on a LAN. (Games on the internet typically use TCP/IP, although they can also use IPX/SPX)
    Community standards do not maintain themselves: They're
    maintained by people actively applying them, visibly, in public. - Eric Raymond

  6. #6
    Registered User
    Join Date
    Apr 2001
    Location
    Winnipeg, Manitoba Canada
    Posts
    106

    Post

    O.k. You DO NOT have to have "Client for Microsoft Networks" as your primary logon. As long as it's in networking, you're golden. Have a user created on your 2k box and use that user yo login or login automatically on the Win98 box. Share a directory on the 2k system, and make sure that your permissions are set so that the user/ or group that the user you created belongs to has rights to the share. Done and done... <IMG SRC="smilies/biggrin.gif" border="0">
    Don't even ask why they call me stressball....

  7. #7
    Registered User
    Join Date
    Dec 2000
    Location
    Ontario, Canada
    Posts
    343

    Post

    as long as u have changed the default shares to get rid of the $ sign you are safe, the $ sign tells it not to be shared on the network if that makes any sense at all? ... mine shares are
    home\storage (D <IMG SRC="smilies/smile.gif" border="0"> and home\home (C <IMG SRC="smilies/smile.gif" border="0"> because the original settings would not allow it to be seen on network..try that?
    "Knowledge belongs in the hands of the people"

  8. #8
    Registered User
    Join Date
    May 2001
    Location
    New Orleans
    Posts
    290

    Post

    Originally posted by Captain Kirk:
    <STRONG>O.k. You DO NOT have to have "Client for Microsoft Networks" as your primary logon. As long as it's in networking, you're golden. Have a user created on your 2k box and use that user to login or login automatically on the Win98 box. </STRONG>
    Whoops...you are absolutely correct on this. Thanks for catching me on this goofup. I was really tired when I wrote this I guess.

    As you said above, as long as it's in networking, you're golden. But let me clarify the wording because it took me a couple of minutes to catch what you were saying. As long as it (Client for MS Networks) is installed and bound to the NIC for your LAN, you can log into a Win2K network.
    Community standards do not maintain themselves: They're
    maintained by people actively applying them, visibly, in public. - Eric Raymond

  9. #9
    unknownGHOST
    Guest

    Talking

    this wont help any, i just thought i'd post the thanks. i've been fighting with this same exact situation for a while now...i eventually gave up on it even after posting questions in forums. next time i goto the WasteLAN, i'll know how to fix the problem. THANK YOU <IMG SRC="smilies/biggrin.gif" border="0">

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •