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.
Got a Linux Box with Samba (2.0.7) and a Windoze 98 box. Both are in the same workgroup, and no domain is set up.
Linux can see Windoze shares, but Windoze does't seem to know that Linux exists. Here's the meat.
Using the 'smbclient -L' command, both boxes come up as being in the same workgroup, and both relay that they are the master browser. However, 'nmblookup -M -' produces that Linux thinks that Windoze is the master browser.
BUT, if I disable the browse master on Windows, then the Network is not accessible at all (from Windoze).
I've tried all sorts of smb.conf variations: WINS support, no wins support, preferred master, local master, os level, and I've stripped everything away but the basics (workgroup=workgroup), and still no luck. I have an encrypted password file and the option set to 'yes.' I can ping back and forth till the cows come home. I've enabled the WINS server on Widows and pointed it to the Linux IP. No luck with or without it.
It seems that Windoze can't resolve the Linux IP to a name, even though I have it in the lmhosts.sam and host.sam files (am I doing the sam files wrong?). On the linux box I can ping Windoze by machine name, but Windoze can only ping Linux with the IP.
Sounds to me like you need to put some info in c:\windows\hosts!! hosts.sam and lmhosts.sam are SAMple files - remove the .sam bit! I think that if you sort that one out the rest will fall into place... Have you enable clear text passwords on Windows yet? If not then that'll be your next mission - there is a .reg file available with your Samba documentation that you'll want to look at.
You files should have no extension - remove the .txt bit and all should be good.
Quote:
Originally posted by matt On the Linux box, when I run the command:
# nmblookup -SR Linux
I get...
querying Linux on 192.168.1.255
name query failed to find name Linux
But...
Uhm... 192.168.1.255 isn't a valid IP address for a machine!! That's the broadcast address for the 192.168.1.0 network... That might also cause you problems... You should only use IP ranging from 192.168.1.1 and 192.168.1.245 on your LAN, (.255 being the broadcase and .0 being the subnet address).
Howdy again! Just checked out you webpage - I dig the webcam on your street!
Anyways - I think we're getting somewhere now. This might help.
My Linux IP is 192.168.1.1
And Windows is 192.168.1.2
sub: 255.255.255.0
When I do "# nmblookup -SR Windows" I get:
querying windows on 192.168.1.255
192.168.1.2 windows <00>
looking up status of 198.168.1.2
received 6 names
(name tables here)
num_good_sends=0
num_good_received=0
But no good on Linux.
Thanks for the quick reply! I've really been bangin' the head against the wall here!
)M.
Originally posted by matt Howdy again! Just checked out you webpage - I dig the webcam on your street!
I may get around to turning it on again some day soon and pointing it somewhere more interesting...
As for nmblookup, here is what I get
Code:
root@mnemosyne:~# nmblookup -S mnemosyne
querying mnemosyne on 192.168.1.255
192.168.1.2 mnemosyne<00>
Looking up status of 192.168.1.2
received 7 names
MNEMOSYNE <00> - B <ACTIVE>
MNEMOSYNE <03> - B <ACTIVE>
MNEMOSYNE <20> - B <ACTIVE>
..__MSBROWSE__. <01> - <GROUP> B <ACTIVE>
WORKGROUP <00> - <GROUP> B <ACTIVE>
WORKGROUP <1d> - B <ACTIVE>
WORKGROUP <1e> - <GROUP> B <ACTIVE>
num_good_sends=0 num_good_receives=0
which suggest that infact it does do a brodcast (hence 192.168.1.255) to get a name lookup... So I'm not sure what to suggest... Do you still get the same problem even with the hosts files setup correctly??
Thanks to proper hosts and lmhosts files on the Windows side, I can now ping Linux from Windows by name (whereas before I had to enter the IP#). But still no luck seeing Linux in Network Neighborhood.
I still get the "name_query failed" message on Linux with the "nmblookup Linux" command. Is the Linux box somehow unable to resolve it's own name and IP address? I'm having a hard time troubleshooting this one.
)M.
ps. On the Linux box I can "smbclient" to shares on Windows and the same Linux box. Odd?
The only entry today in either of the log files is in the samba-log.smb file:
smbd/files.c:file_init(215)
file_init:Information only:requested 10000 open files, 1014 are available.
This seems to be popping up quite a bit in past entries too, though I don't know what it means. I've been messing around so much with the smb.conf file, I don't know how much relevance previous entries have.
Once upon a time (week or more ago) I was seeing Linux in the Network Neighborhood, but wasn't able to acceess it. Around the time that was happening, I was getting rejected user entries in the log file. But now I don't even see Linux from Windows.
There are also entries for being unable to find Domain Master Browser and browse list for the Workgroup from the other week.
Talked to a buddy of mine who does a lot of Linux Admin for a living, and he said I was basically missing a bunch of packages. So, I just rebuilt the box as a Server (did Workstation install before), and we'll try this again!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
Dueling Browse Masters?
