Re: debian-user-digest Digest V97 #890
hello, well I've went through some considerable pains to install the latest samba on my system its there... everything seems to be working fine (seems to be) the client can see the server the server and the client like to talk back and forth... however when it comes to the issue of passwords... it no longer like me I'm running shadow passwords... I have netatalk already installed for the MacIntoshes on my system and I'm also running quotas. Does anybody have any suggestions... I have tried every step in the "Diagnosing Samba" documentation and I always get a failure of password... I have changed and tried my password in upper and in lowercase letters etc. etc. etc.does anybody else have this problem or am I the only one? -------- Andrew Brigham [EMAIL PROTECTED] Northroute Networks Domain=[WORKGROUP] OS=[Unix] Server=[Samba 1.9.17p2] first SMBtconX failed, trying again. ERRSRV - ERRinvnetname (Invalid network nam e in tree connect.) SMBtconX failed. ERRSRV - ERRinvnetname (Invalid network name in tree connect.) Perhaps you are using the wrong sharename, username or password? Some servers insist that these be in uppercase -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: debian-user-digest Digest V97 #890
> > Domain=[WORKGROUP] OS=[Unix] Server=[Samba 1.9.17p2] > > first SMBtconX failed, trying again. ERRSRV - ERRinvnetname (Invalid network > > nam > > e in tree connect.) > > SMBtconX failed. ERRSRV - ERRinvnetname (Invalid network name in tree > > connect.) > > Perhaps you are using the wrong sharename, username or password? > > Some servers insist that these be in uppercase > > Am I to infer from the message above that you're having difficulty only with > smbclient, not when accessing a share from a M$ box? Are you trying to talk > to a computer running NT 4.0 with service pak 3? No I'm having trouble with passwords... I have no NT box on my system I can see all public directories... but I can't get into any of my password protected directories... I can't get in using smbclient and I can't get in using a 95 computer. Andrew Brigham [EMAIL PROTECTED] Northroute Networks -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: debian-user-digest Digest V97 #890
> Ok, let's get everything straight then. You're trying to access a > share on a Win95 box from your Linux system, right? You say that you > can "see" all the shares on the Win95 box you're trying to access. > Does this mean that when you type: > > smbclient -L target-win95-box > you see a list of the shares? If you're seeing the shares from a > Win95 box, try the above command and get back to us. (Include the > output of the above command as well, if you please.) nope I'm targeting my server... I can't get authenticated by my server on the linux box... I can see all the shares on the linux box from my 95 computer and also in smbclient from 2 other linux computers... but I can't get into the password protected directories like my home directories.. - Andy -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Unidentified subject!
> So, I would hate to see the continuation of a proprietary solution to > a particular problem by the free software development population of > the general public. It goes against nearly every basic part of the > Linux/Unix/IP philosopy and in the end denies us functionality and > choice. > > Again, I apologize for the speech. You all seem to be missing the point. Have any of you tried ICQ in the last little while? I recommend you try it before even bothering to suggest such a clumsy and poorly written protocol like IRC. 1. Easy to use. 2. Its a Swiss Army Knife for communications (meaning it does almost everything as far as chatting goes) 3. Shows when friends are on. You don't have to worry about dynamic IP addresses. However, I also agree with the lines I quoted above. I don't believe in proprietary solutions (They don't always fit my needs so its easier to make changes when I have the source). We have many standards which cover most of what ICQ does. But we don't have anyway to bind them together into a seemless communications tool that allows us to communicate with each other regardless of IP number (nothing as smooth as ICQ, that is). Microsoft and Netscape have both built suites that don't impress me compared to ICQ. ICQ is a good model of what I think the future brings in communications. ICQ is a little slow, the company seems to have number of problems trying to keep its system running. But it is still a good idea. As long as we continue to recognize good ideas... We will continue to create better software. I don't apologize for the speech. ______ Andrew Brigham [EMAIL PROTECTED] System Administrator FoxNet Communications -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Merit Radius The Debian Package
Is it just me or does debian Merit Radius package come with a precompiled no shadow password default Long sentence to say... Its not working with my shadow passwords... ??? I've compile merit radius by itself before and it gave me an option for shadow passwords in the Makefile... I would assume that most internet service providors who are using Debian Linux as there Radius server would want to have Radius with shadow passwords... Or am I wrong in assuming that most who do this also use the very same system for both mail and shell access? Is there any easy switch... that the debian guys have added or do I still have to download the source _____ Andrew Brigham [EMAIL PROTECTED] FoxNet Communications -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Radius Merit the ongoing battle
1. I installed Merit Radius 2. I realized I wasn't allowed to use shadow passwords 3. I downloaded the source and fixed the shadow thing in the Makefile 4. I managed to get the server running nicely 5. I did a killall -HUP radiusd-merit 6. Merit stopped sending information to the logfile I retried 5 and 6 numerous times. It seems Merit Radius doesn't want continue adding to the logfile after a killall -HUP The version number is 2.4.23C Any suggestions would be greatly appreciated??? _____ Andrew Brigham [EMAIL PROTECTED] FoxNet Communications -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
