Announcement

Collapse

Forum Rules and Etiquette

Our mission ...

This forum is part of our mission to promote the preservation of vintage computers through education and outreach. (In real life we also run events and have a museum.) We encourage you to join us, participate, share your knowledge, and enjoy.

This forum has been around in this format for over 15 years. These rules and guidelines help us maintain a healthy and active community, and we moderate the forum to keep things on track. Please familiarize yourself with these rules and guidelines.


Rule 1: Remain civil and respectful

There are several hundred people who actively participate here. People come from all different backgrounds and will have different ways of seeing things. You will not agree with everything you read here. Back-and-forth discussions are fine but do not cross the line into rude or disrespectful behavior.

Conduct yourself as you would at any other place where people come together in person to discuss their hobby. If you wouldn't say something to somebody in person, then you probably should not be writing it here.

This should be obvious but, just in case: profanity, threats, slurs against any group (sexual, racial, gender, etc.) will not be tolerated.


Rule 2: Stay close to the original topic being discussed
  • If you are starting a new thread choose a reasonable sub-forum to start your thread. (If you choose incorrectly don't worry, we can fix that.)
  • If you are responding to a thread, stay on topic - the original poster was trying to achieve something. You can always start a new thread instead of potentially "hijacking" an existing thread.



Rule 3: Contribute something meaningful

To put things in engineering terms, we value a high signal to noise ratio. Coming here should not be a waste of time.
  • This is not a chat room. If you are taking less than 30 seconds to make a post then you are probably doing something wrong. A post should be on topic, clear, and contribute something meaningful to the discussion. If people read your posts and feel that their time as been wasted, they will stop reading your posts. Worse yet, they will stop visiting and we'll lose their experience and contributions.
  • Do not bump threads.
  • Do not "necro-post" unless you are following up to a specific person on a specific thread. And even then, that person may have moved on. Just start a new thread for your related topic.
  • Use the Private Message system for posts that are targeted at a specific person.


Rule 4: "PM Sent!" messages (or, how to use the Private Message system)

This forum has a private message feature that we want people to use for messages that are not of general interest to other members.

In short, if you are going to reply to a thread and that reply is targeted to a specific individual and not of interest to anybody else (either now or in the future) then send a private message instead.

Here are some obvious examples of when you should not reply to a thread and use the PM system instead:
  • "PM Sent!": Do not tell the rest of us that you sent a PM ... the forum software will tell the other person that they have a PM waiting.
  • "How much is shipping to ....": This is a very specific and directed question that is not of interest to anybody else.


Why do we have this policy? Sending a "PM Sent!" type message basically wastes everybody else's time by making them having to scroll past a post in a thread that looks to be updated, when the update is not meaningful. And the person you are sending the PM to will be notified by the forum software that they have a message waiting for them. Look up at the top near the right edge where it says 'Notifications' ... if you have a PM waiting, it will tell you there.

Rule 5: Copyright and other legal issues

We are here to discuss vintage computing, so discussing software, books, and other intellectual property that is on-topic is fine. We don't want people using these forums to discuss or enable copyright violations or other things that are against the law; whether you agree with the law or not is irrelevant. Do not use our resources for something that is legally or morally questionable.

Our discussions here generally fall under "fair use." Telling people how to pirate a software title is an example of something that is not allowable here.


Reporting problematic posts

If you see spam, a wildly off-topic post, or something abusive or illegal please report the thread by clicking on the "Report Post" icon. (It looks like an exclamation point in a triangle and it is available under every post.) This send a notification to all of the moderators, so somebody will see it and deal with it.

If you are unsure you may consider sending a private message to a moderator instead.


New user moderation

New users are directly moderated so that we can weed spammers out early. This means that for your first 10 posts you will have some delay before they are seen. We understand this can be disruptive to the flow of conversation and we try to keep up with our new user moderation duties to avoid undue inconvenience. Please do not make duplicate posts, extra posts to bump your post count, or ask the moderators to expedite this process; 10 moderated posts will go by quickly.

New users also have a smaller personal message inbox limit and are rate limited when sending PMs to other users.


Other suggestions
  • Use Google, books, or other definitive sources. There is a lot of information out there.
  • Don't make people guess at what you are trying to say; we are not mind readers. Be clear and concise.
  • Spelling and grammar are not rated, but they do make a post easier to read.
See more
See less

Accessing Win10 Network share from Win98se

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Accessing Win10 Network share from Win98se

    Has anyone been able to "Map A Network Drive" on a Win98 machine to access a shared drive on a Win10 machine? I can go the other way, i.e. my Win10 machine can access shared drives on my Win98se machine no problem. But, when I try to access a shared drive on the Win10 machine from Win98, I get a message stating that a password is required and when I enter a password for the admin on the Win10 machine I get an incorrect password error.

    #2
    I've had this issue before, you have to fiddle with the "advanced sharing settings" under the "network and sharing center" in the control panel. Usually turning off password protected sharing and setting the file sharing connection to 40/56 bit encryption allows older versions of Windows to connect to shared directories.

    Sometimes though you'll have to create a new user account on the shared machine and create privileges for that account.

    Comment


      #3
      Yup, I've tried all of those things, repeatedly. No Joy. Thank you for the reply though. I may just need to get my tweener going again.

      Greg

      Comment


        #4
        I don't have any experience with this, but have you tried enabling SMB 1.0 in "Turn Windows features on or off" ? Windows 10 uses a later version of SMB and later builds disable this apparently.

        Comment


          #5
          Originally posted by gonk23 View Post
          I don't have any experience with this, but have you tried enabling SMB 1.0 in "Turn Windows features on or off" ? Windows 10 uses a later version of SMB and later builds disable this apparently.
          I've also not had experience with accessing shares on windows 98 to a Windows 10 machine, however I did have this exact issue with 98 accessing Samba network shares on my NAS. The issues with my Samba share were related to needing support for lanman, which in my case were fixed by enabling lanman authorization. ('lanman auth = yes'). In Samba, when this setting is not enabled, only clients which support NT password hashes (ie. NT/2000/etc) can access. Unfortunately how this works in Windows 10, I don't know. I only know the way to fix it on a true Samba file share.

          A quick search on the topic brought this up, which might direct you to how to fix it. I assume you need to support LM & NTLM.

          https://docs.microsoft.com/en-us/win...tication-level

          It looks like the default is to support NTLMv2, which is most likely your problem.
          -- Brian

          Systems: Amstad PCW 8256, Apple IIe/II+/GS/Mac+/Mac 512k, Atari 800/520STFM, Commodore 64/128/Amiga 3000/PET 4032/SX-64, IBM PS/1 2121-B82, Kaypro II, Osborne 1, Tandy 1000 SX, TI-99/4A, Timex Sinclair 1000, TRS-80 Color Computer 3/Model 4 GA

          Comment


            #6
            Microsoft turns of NTLMv1 by default now. This is because there are some pretty scary security flaws in it, which have been leveraged to spread quite a few things, most notably ransomware in recent years. Windows 98 can only use NTLMv1 and not v2 which Windows 10 uses, but the Win10 machine can still connect to v1 shares. Hence your ability to go Win10 -> Win98 but not the other way around.

            I would not recommend enabling v1 on your Windows 10 machine and just push files to your win98 machine, and not the other way around. This is especially true if your Win10 machine is portable and will end up on other networks or has some public exposure on the file sharing side of things.

            IBM 5160 - 360k, 1.44Mb Floppies, NEC V20, 8087-3, 45MB MFM Hard Drive, Vega 7 Graphics, IBM 5154 Monitor running MS-DOS 5.00
            IBM PCJr Model 48360 640kb RAM, NEC V20,, jrIDE Side Cart, 360kb Floppy drives running MS-DOS 5.00
            Evergreen Am5x86-133 64Mb Ram, 8gb HDD, SB16 in a modified ATX case running IBM PC-DOS 7.10

            Comment


              #7
              Well, there's always ftp and ssh; I believe that both platforms support the former--and possibly the latter.
              Reach me: vcfblackhole _at_ protonmail dot com.

              Comment


                #8
                As above, Windows 10 will connect to Windows 98PCs however and I recommend just doing it in that direction, setup the share on Windows 98.

                Another option is to get a little cheap Core 2 Duo machine, install Linux, install Samba, setup a share and turn off all those pesky security measures - then both the Win10 and Win98 box can see it, and it's not full of your personal documents. Some of the mini office machines are good as they're power efficient and quiet, one of mine uses a laptop power supply.
                Twitter / YouTube

                Comment


                  #9
                  Originally posted by Chuck(G) View Post
                  Well, there's always ftp and ssh; I believe that both platforms support the former--and possibly the latter.
                  Yes, I did FTP with Filezilla server on the Win10 PC and Filezilla client on the Win98 PC (Internet explorer is horrible with maintaining the connection to Filezilla server. It keeps failing without notice because evidently the password needs to be re sent). It works OK but not possible to run a program from the network. It must be downloaded and then ran locally.

                  Originally posted by SpidersWeb View Post
                  ...Another option is to get a little cheap Core 2 Duo machine, install Linux, install Samba, setup a share and turn off all those pesky security measures - then both the Win10 and Win98 box can see it, and it's not full of your personal documents. Some of the mini office machines are good as they're power efficient and quiet, one of mine uses a laptop power supply.
                  Thank @SpidersWeb, this sorta what I did. In a previous reply I said "I may just need to get my tweener going again.". My previous Tweener started having hard disk issues so I have been not wanting to turn it on until I have the time to back it up completely.

                  The following is the work around that I've come up with for now. Let me know what you guys think security wise.
                  1. Install Oracle Virtual box on the Win10 PC
                  2. Create a Win2000 Pro Virtual PC
                  3. Share a folder on the Win2k VM that the host (Win10) and the Win98 PC can access via a bridged network connection between the VM Virtual NIC and the Host WIFI NIC.


                  This is slightly cumbersome because the VM needs to be started and run in the background(minimized) each time the Win10 PC or the Win98 PC need to access the shared drive. But it does work pretty well indeed.

                  Anyone know how to get the VM to start automatically? In older versions of windows I would just put the shortcut in the startup folder but I cant figure that out with Win10.

                  Thanks again for all of the responses,

                  Greg

                  Comment

                  Working...
                  X