Hi there, I've been listening into your thread, and would like to add this. I have many occasions where WinBloz95 appears to have the network driver properly installed. The server can be found but various parts of the network can't be seen. Everything "seems" to be installed OK, however, it really isn't. Upon going into the network property sheet and deleting all related items and "reinstalling" the card drivers, client and protocol stacks, the rest of the network "Magically Appears(tadaaa)". However, you might have to do this upwards of five or six times to get it to properly write to the registry. It the last step of "writing to the database" that usually fails. This drove me nuts at one account and that is how I remedied it. I did nothing different reloading, just did it over and over again. Good Luck! -ted 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).
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?
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?
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?
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).
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e