Some reaction Leon Leon McClatchey wrote:
Thanx Ray:-)
Raymond Doetjes wrote:
In some cases, you have to switch on: LM announcing in your Windows 95 file and printer sharing service. (You've got that running apparently.)
I just checked the Networks icon in Win95 control panel, and the LM Announcing is set to yes, (Which brings up another question, why can't I access the file areas that I have tagged as shared on the win95 box from the linux box. I do have all the shares set up on the win95 at the "user" level). RAY-> Probably you don't run the smbclient correct. (THIS ONE IS REALLY STRANGE IT DOESN'T USE A STANDARD UNC)
Try smbclient \\\\win95\\myshare That will work. Same goes for your windows 95. When you probably type net use x: \\linux\myshare it will make an X drive.
About dialing the internet, you are right Windows clients and servers rely on NetBios naming, first they try to find the names in - Via an DNS server (Within a Windows NT network when you enabled DNS lookup for WINS). - If fails via an Wins Server - If fails via LMHOSTS records (name and ip address) - then they start a networkbraodcast (this triggers your diald).
Is there any advantage to having DNS lookup activated on the win95 machine? RAY-> Not really (Since SMB uses NetBios names)
DNS is a faster and more reliable method then the WINS name resolution (JUST AN OTHER MICROSOFT BUG!!!!), so if you have some spare time setup a DNS server on Linux.
I addmit that it is strange that even though you have an LMHOSTS with all ip addresses that it still uses networkbraodcasts.
I found that strange too, and am a bit confused along those lines, as from what I've read, Linux and Win95 does not share the same format for the lmhost file?
From what I read in the linux documentation, LMhost is basically "HOST IP ADDRESS", but the win95 LMhosts requires additional parameters as well to signify type of connection or whatever?
Ray-> Don't go and fiddle around with LMHOSTS. Just enter the WINS address of your Linux box. Of if you have setup DNS also DNS!!!
But you can easiliy solve this problem by letting SaMBa beeing the wins server. (I recall it is wins support = yes) then samba is a Wins name server. All you gotta do is tell windows 95 client were to find a wins server in IP configuration.
I do have "wins support = yes" but did not activate the Wins name server on the samba box since in the docs it said something about if I did that, I could cause a loop. Not sure how that would happen with only 2 machines on the network? RAY-> On monday I will send my SaMBa configuration file to you. (I got it at work, at home I don't use Windows anymore, so no need for SaMBa).
I have done the same at my work, it works great. My primary Wins server is the NT server (yuk) and the secondary Wins server is the SaMBa Linux server (yeah).
Thanx Loads, I got a print out of your message and will use it as I dig through all the configuration files to make sure everything is right:-)
RAY-> There was another tip on this mailing list asswell. You might wanna throw away all network settings from your Win95 box. Then reinstall everything. Then also your netware error might be gone. (I recall now, that in my Novell managing days I had a few Windows clients that could'nt browse the network also. I did the same thing I threw away all network settings and re-installed them (and all of a sudden it was there)). Otherwise you might wanna re-install your windows completly. Because this is surelly a Windows PROBLEM
-- cya l8r Leon McClatchey leonmcclatchey@homemail.com Linux User 78912 (Win95 Box)
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e