Discussion Locked

NetBIOS security problem over dialup.

0 helpful
10 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
When running a PC on a LAN with a dialout internet connection, we want to allow netbios over the LAN but not on the dialup. However, if you edit the properties for the TCP/IP protocol bound to the dial-up adapter and uncheck the netBIOS box, this also disables netBIOS on the LAN! Is there a way to make windows close down ports 138 & 139 on the dial-up without adding more protocols or 3rd party software? To amke things harder, this problem only appears on some PCs...

10 replies

by shanghai sam

I need more information to help you exactly, your dial out, I presume, is to an ISP. which OS are you dialing from? NTws, NTser, 2kser, 2kpro?
number 2, what kinds of workstations do you have?
and what is the binding order on their NIC's?
and another short answer is yes,
we have Ositis Winproxy and it works awesome as a small NAT and firewall, for a smaller office,, but you shouldn't need that if you already have a proxy connected to your ISP, which I'm assuming you do...

by michael roark - ccna/da mcp 3csa

I need more information to help you exactly, your dial out, I presume, is to an ISP. which OS are you dialing from? NTws, NTser, 2kser, 2kpro?
number 2, what kinds of workstations do you have?
and what is the binding order on their NIC's?
and another short answer is yes,
we have Ositis Winproxy and it works awesome as a small NAT and firewall, for a smaller office,, but you shouldn't need that if you already have a proxy connected to your ISP, which I'm assuming you do...

by buffalodan

in the properties for the tcp/ip bound to the "dial up adaptor", unselect "client for microsoft networks"....
you do not need to use the microsoft networking client when accessing the internet.
The binding stack looks like this....
Hardawre>boundto Protocol>bound to >Client

For an excellent tutorial on securing microsoft machines on the internet, visit steve gibson's web site Via gibson research.
(the producer of zonealarm)

www.grc.com

by drose

Sorry, I should have mentioned this earlier -- No clients/services whatsoever are bound to the DU adapter's TCP/IP protocol. Under the NIC's TCP/IP protocol the net bios box is always on and is always greyed out. Netbios is active over dialup. turning off this check box for the dial-up TCP disables netbios completely. This doesn't happen on all PCs but when it does happen there's no fix I can find (reinstall everything, winsock 2, different LAN card etc) so it seems to be hardware related in some way but I'm completely stumped.

by maxwell edison

Windows networks use a system of shared files and printers based upon the SMB (Shared Message Block) protocol. This protocol is deployed within the Windows NetBIOS protocol, which in turn, is installed by default over TCP/IP in the first versions ofWindows95 and Windows 3.11 for Group Work.

This characteristic becomes a security problem when systems using Windows networking shares connect to an unreliable network such as the Internet. In such cases, any Internet user can attempt to access the Windows system NetBIOS services remotely through the TCP/IP and access the resources if these have not been adequately protected.

There is the possibility that in certain local network configurations it may be necessary to install NetBIOS over TCP/IP and in order to counteract the security problem, it becomes essential to establish password accesses to all shared resources. This way, a user outside the system will not know the password and therefore will be unable to access such resources from outside the system.

In order to check if you have NetBIOS installed over TCP/IP in your Win9x system, look up its properties in (Start -> Configuration -> Control Panel -> Network -> TCP/IP -> Properties -> NetBIOS tab), where there is a check box that allows you to disable it. This prevents an Internet user from accessing shared resources on the local network. Another way of checking whether we are exporting NetBIOS to the Internet is to launch the command NETSTAT -A (in MS-DOS) and seeif the ports 137, 138 and 139 appear.

In any case it is advisable to install the more recent versions of operating systems, which have as general rule taken care of these types of problems.

Maxwell

by drose

Well as it turned out noone could help me. I should have made it clear that I was using windows 95, and that TCP/IP existing only for routing via wingate, netbeui was used for all "regular" internal traffic.

"change the operating system" is not considered an acceptable answer to problems when I give it, and I was surprised to hear it here.

"Buy a third party product" also will change the situation but is not a fix for the specific problem I described.

In anycase, I am now running E-smith 4.12 as a NAT router on a 486 (www.e-smith.org) and it has the nice side effect of giving me a higher throughput on the modem -- I highly recommend it for all LANs.

Thanks everyone for all your answers, but I don't see any here which fix the problem I was having. Cheers!

This discussion is closed to new replies.