Netbeui Windows 10

[Billy Habash]

HelloI am interested in bringing a Windows 95 machine up to current day Microsoft networking status. The WIN95 machine has straight-up NETBEUI/NETBIOS that came with Windows 95 OSRv2. Research leads me to understand this protocol died, with it's final nod during the days of Windows XP.

I have the Win95 PC Ethernet card connected directly to an interface on a laptop using windows 11. I installed TCP/IP on the Win95 machine. I am able to ping on both ends and get a reply. That is a ping command from DOS on win95 machine to IP address interface of laptop interface results in 4 replies/no loss and vice versa if issuing from the Windows 11 laptop.

For 9x 137 and 138 UDP are used for name resolution if not using DNS. Port 139 TCP used for filesharing.

Ports 137 and 138 are still listening on newer Windows operating systems.

Port 139 is still used for file sharing on even the latest Windows operating systems for backwards compatibility but the security settings on the newer operating systems will prevent file sharing.

Netstat should work on 9x, try it and see.

WINS can still be used even on the latest Microsoft Operating systems and the WINS server on those operating systems are backwards compatible.

You don't need a WINS server on a home system unless you want it. A system in the same subnet will be the master browser and/or you can use a host file if you need to.

Any time I've done file sharing from an old OS to newer MS OS I've re-enabled SMB1, I haven't tried to disable SMB1 and try to still share files with these older operating systens. Even with SMB1 disabled port 139 will still be listening on the newer OS.

So yes, everything is available it's just that the newer OS either has SMB disabled or has the security settings set to not allow access. You can disable that security.....but you've left the system vulnerable unless you account for that with a firewall. It won't be too long before both Linux and Windows remove support entirely for SMB1, it hasn't happened yet but it's slowly occurring with Linux removing things and MS disabling things by default.

What I do is leave the client operating systems alone and re-enable SMB1 and the required settings on my TrueNAS server. I haven't bothered with using ACL w/ VLAN or air-gapped networks, if they can break past my pfsense and compromise my TrueNAS (based on FreeBSD) then they would likely be able to compromise anything else as well. Windows relies alot on SMB for functionality whereas Linux does not so it makes far more sense to do the filesharing on Linux vs Windows for

Thanks. After using netstat I noticed the corresponding ports were open and this was true on both Win95 and Win11 machines. Then I tried nbtstat -A 192.168.x.x and could see computer name, user, and name of network on the Win95 machine. That's when I realized the two nodes were communicating over the network. So, I sought the folder made on the windows 11 machine and did not find it. So, I created a shared folder on the windows 95 machine and it could be accessed by the Win11 PC. Then I could send the CD-ROM. 508 MB at a rate of 130KB/s. I checked on the Win95 PC which now has the CD-ROM ISO.

Earliest PC I have is Windows For Workgroups 3.11, latest is Win10. Only protocol installed is TCP/IP (maybe IPX for some games but I don't bind this to file/print sharing) and am able to share files between all OS's

browsing doesn't really work but typing the ip eg \\192.168.1.1 will bring up the machine. Sometimes it only works one way like what your seeing but that's good enough for me.

Like dosfreak I simply enable smb1

We are looking at disabling Netbios over TCP/IP on some of our Windows 2008 application servers. Since we don't use WINS, the server will be sending broadcasts for name resolution as far as I understand.

For purely-NetBIOS-based services, if there are any, disabling NetBIOS-over-TCP would probably either completely disable the service or force it to use the NetBIOS Frame (NBF) protocol, which only works on the same LAN segment as the server. I don't even know whether Windows 2008 supports NBF; I don't think modern versions of Windows do, although I think some of them can run the NBF driver from older versions of Windows. Name resolution for NBF is broadcast-based, but doesn't run over IP.

For SMB/CIFS file service, disabling NetBIOS-over-TCP would still allow SMB to run directly over TCP on port 445. Name resolution for SMB-over-TCP would be done using DNS, which isn't broadcast-based. SMB/CIFS can also run over NBF; as indicated, NBF name resolution is broadcast-based.

Note that "NetBIOS-over-TCP" really means "NetBIOS-over-IP" or "NetBIOS-over-TCP-and-UDP", as UDP is used for name resolution and the NetBIOS datagram services. If you want to see whether there is any NetBIOS-over-TCP name resolution happening after you disable NetBIOS-over-TCP on the server, look for packets going to or from UDP port 137; you can use a capture filter of "udp port 137" for that (the display filter would be "nbns", for "NetBIOS Name Service").

If you want to check for NBF traffic, then, at least with sufficiently recent versions of libpcap/WinPcap being used by Wireshark, a capture filter of "netbeui" (or a display filter of "netbios") would work. (Yes, both NetBEUI and NetBIOS are the wrong terms for NBF, but that's what libpcap and Wireshark are using.)

A capture filter of "broadcast" will check for all LAN broadcasts. If you only want to find out how much NetBIOS-over-TCP broadcast name resolution is occurring, try "broadcast and udp port 137" when capturing.

And, yes, you should be able to use Wireshark to see how much NetBIOS-over-TCP broadcast name resolution is occurring; just compare the results of capturing with "broadcast and udp port 137" with NetBT enabled and with NetBT disabled.

The status bar (at the bottom of the window) has 3 sections; the middle section has the number of packets in the capture and the number of those packets that are being displayed. If you used the capture filter, the number of packets in the capture would be the number of NBNS broadcasts; if you used the display filter, the number of displayed packets in the capture would be the number of NBNS broadcasts.

This tweak is used to install NetBeui a easy way to network computers at home without having to worry about configuring ip addresses etc, it enables windows 98 and earlier to communicate with XP. you can get the files of the XP CD or follow these instructions...

If you own a Google Chromecast streaming device, you can easily share a browser tab in Chrome browser or even your entire desktop. This can be very useful when presenting from your laptop or if you just want to watch something on a big screen that is only on your PC. The only requirement is you must be on the same network as your Chromecast...

If you are a fan of minimalist desktop experiences, hiding the desktop icons are an easy way to clean up the Windows interface. Instead of saving everything to your desktop, use the default profile folders such as downloads and documents. Actually hiding all the icons on your desktop is a very simple customization hidden in the right-click context menu. Just right-click on the desktop, select View...

Google security researchers have published details about a major security flaw found in the SSL protocol that is used to encrypt data transferred between your browser and a web server. SSL is typically used in situations where logon credentials are validated...

Enabling two-factor authentication is a great way to add an additional level of protection to your Microsoft account. Even if your password is stolen, your account is still protected because two-factor authetication requires an additional level of verification to log in. Microsoft calls their version of two-factor authentication "two-step verification" and it works by providing you with a random code...

When I run the Networking Wizard on my network consisting of two winxp computers it unchecks the Disabled NetBios over TCP/IP box on both computers. On one computer it checks Enable NetBios over TCP/IP and on the other it chooses the default of letting the DHCP server [my router] decide.

According to my understanding I should be able to disable NetBIOS over TCP/IP since I only have winxp computers on my network and winxp attaches its SMBs to TCP/IP differently [i think it's called NetBios on TCP/IP] than Win98 which used NetBios over TCP/IP. I thought NetBios over TCP/IP was necessary only if you were networking w/ earlier Win OS's but I've read a lot of conflicting info on the NetBIOS on or over TCP/IP over the years. Supposedly NetBios over TCP/IP constituted a significant security risk at one point - I don't know if it's still considered a risk currently.

I'd like to know if I should/can disable NetBios over TCP/IP but I don't want to experiment because I just got two-way access after months of troubleshooting and I am very tired of running that Network Wizard and running between 2 computers checking and changing settings. During that troubleshooting I tried enabling NetBios over TCP/IP on both computers for awhile. It didn't help so I disabled it again but apparently the Wizard thinks I need it.

In XP, NetBIOS is used primarily for the Browser Service to allow you to "see" other computers on your subnet and in the same workgroup or domain. Without this enabled, the computer cannot use any broadcast method to discover what's around them and must rely solely on other resolution methods. This is significant when you are trying to share folders from each machine so they are accessible to other workstations on the network.

Theoretically, you can shut down NetBIOS over TCP/IP and still function - and to a point it will, but you'll need to either use an LMHOSTS file or WINS oe local DNS server with WINS integration enabled to be able to browse shares or connect using UNC names rather than IP addresses.

Is the WINS tab giving me the choice between lmhosts or netbios over tcp/ip for file&printer sharing? Can one add an lmhosts file and enable netbios over tcp/ip? Will the client service check the lmhost file first and if it fails to connect thru lmhosts will it then query the master browser?

3a8082e126