Sorry, wrong again. 😁

Here's what I did:

1. Install WfW (network card is autodetected)
2. Install TCP32
3. Remove all protocols except TCP/IP
4. Setup TCP/IP, select DHCP
5. Enter net usershare [...] in Linux shell
6. Open Windows File Manager, map network drive, select share on my Linux PC
7. Done-ski

dosgamer wrote:

5. Enter net usershare [...] in Linux shell
6. Open Windows File Manager, map network drive, select share on my Linux PC

Then you are fortunate enough to have a Linux configuration in which NetBIOS over TCP/IP is enabled by default. 😒
http://www.techradar.com/news/networking/samb … ndows-1154705/2

(Of course there would be no setting in Windows 3.x to enable or disable NetBIOS over TCP/IP, because it is impossible for Windows 3.x to use anything else.)

It's just the default Debian install. Just for shits and giggles, I added disable netbios = yes to smb.conf, made no difference, WfW can still access everything just fine. Anything else? 😁

Sure, since you ask. What ports does "netstat -lntu" show?

Here ya go:

1Active Internet connections (only servers)
2Proto Recv-Q Send-Q Local Address           Foreign Address         State      
3tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN     
4tcp        0      0 127.0.0.1:631           0.0.0.0:*               LISTEN     
5tcp        0      0 127.0.0.1:25            0.0.0.0:*               LISTEN     
6tcp        0      0 0.0.0.0:445             0.0.0.0:*               LISTEN     
7tcp        0      0 0.0.0.0:33320           0.0.0.0:*               LISTEN     
8tcp        0      0 0.0.0.0:139             0.0.0.0:*               LISTEN     
9tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN     
10tcp6       0      0 :::22                   :::*                    LISTEN     
11tcp6       0      0 ::1:631                 :::*                    LISTEN     
12tcp6       0      0 ::1:25                  :::*                    LISTEN     
13tcp6       0      0 :::445                  :::*                    LISTEN     
14tcp6       0      0 :::45374                :::*                    LISTEN     
15tcp6       0      0 :::139                  :::*                    LISTEN     
16tcp6       0      0 :::111                  :::*                    LISTEN     
17udp        0      0 0.0.0.0:51580           0.0.0.0:*                          
18udp        0      0 0.0.0.0:631             0.0.0.0:*                          
19udp        0      0 0.0.0.0:735             0.0.0.0:*                          
20udp        0      0 127.0.0.1:761           0.0.0.0:*                          
21udp        0      0 0.0.0.0:5353            0.0.0.0:*                          
22udp        0      0 0.0.0.0:19824           0.0.0.0:*                          
23udp        0      0 0.0.0.0:38831           0.0.0.0:*                          
24udp        0      0 0.0.0.0:68              0.0.0.0:*                          
25udp        0      0 0.0.0.0:111             0.0.0.0:*                          
26udp        0      0 10.0.0.109:123          0.0.0.0:*                          
27udp        0      0 127.0.0.1:123           0.0.0.0:*                          
28udp        0      0 0.0.0.0:123             0.0.0.0:*                          
29udp        0      0 10.0.0.255:137          0.0.0.0:*                          
30udp        0      0 10.0.0.109:137          0.0.0.0:*                          
31udp        0      0 0.0.0.0:137             0.0.0.0:*                          
32udp        0      0 10.0.0.255:138          0.0.0.0:*                          
33udp        0      0 10.0.0.109:138          0.0.0.0:*                          
34udp        0      0 0.0.0.0:138             0.0.0.0:*                          
35udp6       0      0 :::53947                :::*                               
36udp6       0      0 :::735                  :::*                               
37udp6       0      0 :::44230                :::*                               
38udp6       0      0 :::5353                 :::*                               
39udp6       0      0 :::111                  :::*                               
40udp6       0      0 fe80::21e:64ff:fe40:123 :::*                               
41udp6       0      0 ::1:123                 :::*                               
42udp6       0      0 :::123                  :::*                               
43udp6       0      0 :::55630                :::*

BTW, disable netbios = yes doesn't change any of the ports.

dosgamer wrote:

BTW, disable netbios = yes doesn't change any of the ports.

Well, if it's listening on ports 137-139, that would seem to indicate NetBIOS over TCP/IP is enabled. I can't imagine why it would be listening on those ports otherwise. As to why editing smb.conf has no effect, I would not know. (I assume you're restarting smbd after editing.)

ETA: A little more Googling suggests that nmbd (which is part of Samba) might also have to be stopped/configured.

It is strange that, considering Linux seems to emphasize security, this legacy protocol is apparently enabled by default even when it has no use with modern versions of Windows.

Oh ok, I only issued "service smbd restart", that would explain why it still worked. Yes, it seems NetBIOS is enabled by default in Samba, you have to explicitly add the "disable netbios = yes" line to disable it. Maybe some distros do it? I just checked the distros currently installed on my HDD and neither Debian, Ubuntu nor CentOS disable NetBIOS in their default smb.conf. In any case, I don't see how it's more of a security risk than the rest of SMB, and of course it makes things easy for us retro users. 😁

Very good, you enabled NetBIOS over TCP/IP. Clearly you did not consider that a hassle. 😜

try that with win 10 pc and did nothing same thing happening

Robhalfordfan wrote:

try that with win 10 pc and did nothing same thing happening

You mean you followed the instructions in http://searchenterprisedesktop.techtarget.com … in10-NAS-Access ?

Jorpho wrote:

Robhalfordfan wrote:

try that with win 10 pc and did nothing same thing happening

You mean you followed the instructions in http://searchenterprisedesktop.techtarget.com … in10-NAS-Access ?

yeah followed it and did nothing

Windows 10 is still sold by Microsoft.
MS Tech support should be able to provide you with full help and support.

watlers_world wrote:

Windows 10 is still sold by Microsoft.
MS Tech support should be able to provide you with full help and support.

Come on, seriously? Windows 3.x is not sold by Microsoft anymore and they couldn't care less if you're trying to connect a Windows 3.x computer to a Windows 10 computer.

Ampera wrote:

Try an FTP server. There probably exists a client for Win16. Samba didn't really do much until 95-98, and really was only good on NT5 up.

++ on using an FTP server to move files around. IIRC, the TCP/IP package for Windows 3 includes a FTP client.

tayyare wrote:

This is similar to my experience. I had no problem reaching to a shared folder in a Windows 3.11 or Windows 9x shared folder but not otherwise. But I also am quite sure that not only first two octecs, but first three should be same according to my experience : like 192.168.1. 10 and 192.168.1.15. Being in the same "workgroup" might also help (mine are in the same workgroup but I'm not sure what happens if they were not).

You are correct. Not sure what I was thinking, but yes the first three octets must be in the same.

update

in a recent windows 10 update

it allow to network a real shared drive on real wfw 3.11 machine and copy file to and from it no problem compare to few months ago

Ampera wrote:

Try an FTP server. There probably exists a client for Win16. Samba didn't really do much until 95-98, and really was only good on NT5 up.

This. Was going to post it myself.

Hi,
@dosgamer

I've seen you mentioned your samba server works with windows for workgroups 3.11
I've been fiddling with my smb.conf for days now and I can't get it to work.
Could you maybe share yours so I can see what I do wrong?

Jade Falcon wrote on 2017-11-17, 17:06:

Ampera wrote:

Try an FTP server. There probably exists a client for Win16. Samba didn't really do much until 95-98, and really was only good on NT5 up.

This. Was going to post it myself.

Please just keep in mind that FTP now is generally considered a legacy technology by itself.
Many web browsers et cetera dropped support for it years ago.
Personally, I had to resort to things like wget myself due to this.