Re: [S.u.S.E. Linux] Netware Shell Unavailable, Contact Network Administrator
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.) 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). I addmit that it is strange that even though you have an LMHOSTS with all ip addresses that it still uses networkbraodcasts. 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 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). Goodluck ----------
Van: Leon McClatchey <leonmcclatchey@homemail.com> Aan: suse-linux-e@suse.com Onderwerp: [S.u.S.E. Linux] Netware Shell Unavailable, Contact Network Administrator Datum: donderdag 13 augustus 1998 4:22
Hello Everyone:-)
I've got one little nuisance problem, that I hope someone can help me with:-) I've got a little network going between my Suse 5.1 Box and my Win95 box. I am using the Samba suite with Linux currently my file server and internet gateway. The problem that I've got is actually two-fold (I think).
1: I cannot see my Linux Box in the network neighborhood, but when I do a search for it, then I can "find" it, and access all the file areas that I have defined. It never does show up in the network neighborhood.
2: Everytime Win95 boots and/or someone logs in on the win95 machine, a prompt comes up saying "Netware Compatible Shell unavailable, Please contact your network administrator". Well, I'm the network administrator, and I am unable to find anything on "creating a netware shell" between Linux and Win95?
There are actually a couple of other minor bugs as well, for one, whenever I activate "dial-on-demand", The win95 causes the linux box to keep dialing out on the internet about every 5 to 15 minutes? From what I've read, that may have something to do with the fact that I don't have a "nameserver" running in my little network? Even though I have all the hosts, lmhosts, and network configuration files on both hosts as identical as the operating systems allow?
Thanx Loads:-)
-- 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
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?
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
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
Thanx Raymond:-) Raymond Doetjes wrote:
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.
When I was first setting up smb, The smbclient commands worked as far as viewing the win95 services:-) But, I haven't tried that lately, been trying to mount the win95 shares on my "/mnt/win95/share" as nfs areas? Perhaps via samba, the shares don't show up as nfs areas?
Same goes for your windows 95. When you probably type net use x: \\linux\myshare it will make an X drive.
correct, that works just great, in fact, it seems that everything that I have set up as shares on the Linux box does come thru just great when I want to access those areas:-)The only real problem that I've been experiencing along those lines is that even though I have myself set up to logon to the Linux box with "root privileges" via samba, I still can't do anything as far as monitoring what is being accessed, unless I telenet in and use smbstatus. Then I can see what shares are being accessed and all that good stuff:-) But, I am able to write files in areas that other users are unable to write to (had to make some attrib changes to allow the rest of the clan to save files to some of the defined data areas:-)
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 just got done playing with that, and you know something, I found it to be a pretty good challenge:-) Also started playing with named as well, finally got them both to at least work without erroring out, but still not sure on what to set up and what to ignore:-) After all, I've currently got only two machines on the network:-)
y-> 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!!!
I've got that set up on the win95 box to look to my linux box as Wins Server, but now I get the error about no domain server available (I've got Samba running as both a local and global preferred server), but could not find anything on how to set up the Samba password file, or even where it is located:=(
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 would appreciate it, I would like to get the network working between Linux and Win95 before I throw another Joker on the fire:-) (See if it is possible to add OS/2 as well)
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.
hehe, I've given that some consideration since that is basically how the folks where I bought the machine to get the sound card to work:-) They had to remove all the sound drivers and reinstall it to get the sound card to work:-( (I still have problems along those lines, but that is not very high on my priority list (tho it may on my kids:-)
Otherwise you might wanna re-install your windows completly. Because this is surelly a Windows PROBLEM
I have no doubts along those lines at all:-) And from what I've heard, win98 has even more problems;-0 -- 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
participants (3)
-
leonmcclatchey＠homemail.com -
raymond.doetjes＠tip.nl -
tsm＠wwnet.net