Has anyone encountered the error, "Network is busy" when trying to connect to a Samba share from a Win95 machine? This problem started when I added a second adapter to an IBM G30 running AIX. My WinNT machines connect fine without a problem. I have tried nearly every Smit installable Samba package as well as compiling the three most recent versions and the error is present with all of them. At this point I am certain it must be a bug within the SMB protocol for my particular network setup. Does anyone have even a remote idea as to the cause of this mind-confuction? If I listed everything I have tried it would take 30 minutes to download this email. =) Here is a brief run-down of our network: A token ring consisting of: win95 ver A machines win95 ver B machines Win NT 4.0 wkstns A few Crackintoshes This token ring routes accross an ATM backbone into an ethernet which is where the G30 sits. The G30 has an ethernet and token ring adapter. The ethernet leads to a hub and onto an Advantis, and I must add, HIDEOUS T-1 circuit (this is on a university network and all commercial traffic cannot use the backbone) Thus, I install the second adapter, the token ring, to allow the staff members a local route to the G30 accross the campus backbone because the lag on Advantis is ungodly. (15 - 20% packet loss on a good day) The token ring routes out onto the ATM backbone (three hops from the machines in question) I believe the dual adapter configuration is confusing the win95 client. I have tried the "interfaces" config options in smb.conf with both, and each one by itself. I have specified each of the ip address in the win95 LMHOSTS file. I also tried using that ZANNET SMB package and received the same error. I know what you are thinking, slap WinNT on the 95 cracker-jack boxes. I wanted to, but we require some god forsaken 16 bit publishing software that will not run under NT. Ahhh, the world of Microsoft. Thanks for any help in advance, Stressed to hell, Chuck +~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+ | Chuck Carson ==> 573.884.7161 digmo.org/chuck | System Admin ==>Socket Internet Services www.socket.net | System Analyst ==>Digital Missourian www.digmo.org +~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+~+
Hi I'm new to this list so please bear with me if I'm going over old ground. I've read the Samba FAQ and the document about configuring Win95 clients, both to no avail. I have two Win95 clients which differ in their Network config only in that one has an ethercard which connects via an ISDN router to the Internet. It also has a modem and the Dialup Adapter so I can connect using the modem if the ISDN service is down. I'll call this first the "networked" client. The second is a "standalone" machine which has only the Dialup Adapter i.e. has a modem connection to the Internet. When I boot the "networked" client, it throws up a dialogue and asks that I logon to the network. This I do (simply by pressing Enter as I have set an empty password) although I've never really understood what this means - it can only mean that it is validating the password against a local file as no network activity occurs! If I then attempt to log a network drive (I have a Web server on the Internet running Samba) it works fine. And this is true even if the ISDN line is down, except of course that I have to establish a modem connection first. When I boot the "standalone" client, it does _not_ throw up the "logon to the network" dialogue. And so, when I attempt to log a network drive on the Samba server (having first established a modem connection of course), it refuses immediately and tells me that I am "not logged on"! So my problem is: How do you make a "standalone" client "log on to the network"? I should also point out that the client which works (the "networked" client) was formerly a Win3.1 machine which was subsequently "upgraded" to Win95 whereas the "standalone" client started life (such as it is :-) as Win95. So I'm wondering if what I'm trying to do, and which was very easily set up under 3.1, is not possible with 95? I appreciate that this is more properly a Win95 problem than a Samba one, so perhaps someone could point me in the right direction... TIA John Sutton *********************** John Sutton SCL Computer Services http://www.scl.co.uk Tel +44 (0) 1239 621021 ***********************
>>I have two Win95 clients which differ in their Network config only in >>that one has an >>ethercard which connects via an ISDN router to the Internet. It also has >>a modem and >>the Dialup Adapter so I can connect using the modem if the ISDN service >>is down. I'll >>call this first the "networked" client. The second is a "standalone" >>machine which >>has only the Dialup Adapter i.e. has a modem connection to the Internet. >> >>When I boot the "networked" client, it throws up a dialogue and asks that >>I logon to >>the network. This I do (simply by pressing Enter as I have set an empty >>password) >>although I've never really understood what this means - it can only mean >>that it is >>validating the password against a local file as no network activity >>occurs! If I then >>attempt to log a network drive (I have a Web server on the Internet >>running Samba) it >>works fine. And this is true even if the ISDN line is down, except of >>course that I >>have to establish a modem connection first. >> >>When I boot the "standalone" client, it does _not_ throw up the "logon to the >>network" dialogue. And so, when I attempt to log a network drive on the >>Samba server >>(having first established a modem connection of course), it refuses >>immediately and >>tells me that I am "not logged on"! >> >>So my problem is: How do you make a "standalone" client "log on to the >>network"? I >>should also point out that the client which works (the "networked" >>client) was >>formerly a Win3.1 machine which was subsequently "upgraded" to Win95 >>whereas the >>"standalone" client started life (such as it is :-) as Win95. So I'm >>wondering if >>what I'm trying to do, and which was very easily set up under 3.1, is not >>possible >>with 95?> >In the Network settings in the Control panel there is a section where you >select Windows login, network client etc. That's obviously different in >the two.Sadly not... The two both have Client for Microsoft Networks as primary logon and both are set up identically. I've used the poledit tool on the 95 cdrom to verify that the network config is identical. As I said before, the only difference I can detect is in the histories of the two systems. So in one of them there is loads of stuff in win.ini and system.ini which doesn't exist in the other.... Does anyone have a "standalone" system (i.e. modem only) with which you can successfully mount Samba shares over the Internet? And if so, does it insist that you "logon to the network" when you boot it? Thanks *********************** John Sutton SCL Computer Services http://www.scl.co.uk Tel +44 (0) 1239 621021 ***********************
>Does anyone have a "standalone" system (i.e. modem only) with which you can >successfully mount Samba shares over the Internet? And if so, does it >insist that you "logon to the network" when you boot it?I am able to mount successfully from my "standalone" system and use the "net view \\server" command successfully, even though I cannot browse. Yes, I do have to have the "logon to the network" box checked. If not, I get a message about not being logged on. I suppose you could use the "net logon" command, instead of checking the box? I will test this tonight and let you know if anything I've said is bogus.