Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have spent a LOT of time (I can't believe how badly I underestimated the complexity of setting up Samba) configuring Samba on my Linux box.
I am (finally, after twiddling with my firewall) able to ping eth0 from the Windows client, but nothing appears in my Network Neighborhood. And if I click on "Entire Network", I get the "Unable to browse the network" error.
My Windows client is named "winthing" and the Samba netbios name is "sambathing". Both are setup within the same subnet and have the workgroup setup as "MYWRKGRP".
On the Win98 client, if I ping winthing, I get:
Pinging winthing [192.168.1.128] with 32 bytes of data:
Reply from 192.168.1.128: bytes=32 time<10ms TTL=128
Reply from 192.168.1.128: bytes=32 time<10ms TTL=128
Reply from 192.168.1.128: bytes=32 time<10ms TTL=128
Reply from 192.168.1.128: bytes=32 time<10ms TTL=128
Ping statistics for 192.168.1.128:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Still from Win client, when I ping sambathing:
Pinging sambathing.MYWRKGRP [192.168.1.128] with 32 bytes of data:
Reply from 192.168.1.128: bytes=32 time<10ms TTL=128
Reply from 192.168.1.128: bytes=32 time<10ms TTL=128
Reply from 192.168.1.128: bytes=32 time<10ms TTL=128
Reply from 192.168.1.128: bytes=32 time<10ms TTL=128
Ping statistics for 192.168.1.128:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
These are both the same IP address -- shouldn't they be different? Would that account for why I can't browse the network?
Also, from the Linux box, I can't ping either winthing or sambathing -- I get unknown host errors.
yeah the IP's MUST be different. run 'ifconfig' on linux to check the ip there, and 'winipcfg' on windows. you should ping by ip adress and not name, esp as win9x doesn't really use a host file in teh first place.
Thanks: what do I need to be looking for when I run those commands? And how do I go about fixing the IP addressing problem? (Nice, easy questions, aren't they?...)
Windows is set to get IP from WINS/DHCP, which I have setup on the Linux box. Win ipconfig gives the following:
Are you sure sambathing the name of your linux computer and that it is listed in the smb.conf file as the netbios name?
It seems that your win machine is seeing itself as winthing and sambathing????
Check your network setup on your win computer and make sure the computer name and netbios name for your win machine are both winthing and check your smb.config file to make sure the netbios name there is sambathing.
well, you're pinging windows on both occasions, your linux IP is 192.168.1.100 I'd be curious as to why windows reports 3 interfaces..? if you only do have one card, then you'll want to remove the otehr two setups in the control panel | network. you presumably must have specified the ip for sambathing.blah in windows somewhere, and it's set wrongly. use testparm to test the smb.conf for validity, and you should also have set up password security by either a reg hack in windows: search for enableplaintextpassword, or set password security in samba, and made a smbpasswd.
Samba configuration isn't that complex and hard to think. you can even finish it within 10 minutes or less anyway, all you have to do is edit the file /etc/smb.conf.
here's i wanna share with you. when i configure my samba. i only follow the instructions of on the link which i'm gonna show you below:
just follow everythin' and you'll see the difference. once you're done, all you have to do is take a break and have some drinks to relax, celebrate with a bottle of wine
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
anyway, all you have to do is edit the file /etc/smb.conf.
