necessary to bind TCP/IP to Microsoft network client?

Simon Hyde shyde at
Fri Oct 31 08:27:15 GMT 1997

On Fri, 31 Oct 1997 08:58:21 +1100, you wrote:

>Having some strange difficulties with samba...
>it compiled fine and seems to be running ok but none
>of my win95 client machines can see the samba server.
>They can't even see the samba server when the server
>is configured as a WINS server and the client is
>configured to look at the server as its WINS server.
>anyways, my clients all have the following...
>microsoft network client
>IPX protocol
>TCP/IP protocol
>my office mate says that TCP/IP should not be bound to
>any clients since then that allows the security loop
>hole that people on the outside internet can access
>ourfile systems on the those clients.
>But: If I do bind TCP/IP to the microsoft client I
>*CAN* see the samba server just fine.
>do I *have* to have this binding on the client machine
>in order for samba to work?  I have a feeling that
>samba does everything via TCP/IP and not IPX and as
>a result all the clients around here are going to
>have to bind TCP/IP to microsoft network client and
>thus open up security problems.
Samba only works over TCP/IP, therefore you have to bind the clients to
TCP/IP. However I believe the particular security whole you are talking
about is the winnuke bug, for which there are quite a few fixes hanging
around, just stick 'winnuke' into yahoo and it should flag up some pages
with useful information on how to solve this particular problem.

>Also since all of my machines that I'm trying this with
>are on the same subnet is there any reason I should be
>running any WINS servers?
I wouldn't say so...and if one of them is a samba server you should only
run the one wins server.

More information about the samba mailing list