Nu-Bee
11-02-2003, 01:44 PM
I got over the hump of pulling my hair out & cursing Linux a while back.
Now I just accept most difficulties as they come, and try to work through them without any screaming rants or paranoia about linux.
You know, the love/hate relationship that we won't admit but is there nonetheless. :)
I installed Mandrake 9.2 about a week or so ago, and Samba worked & got configured flawlessly.
For experimental reasons, after I had it installed all this time I reinstalled it a couple days ago.
This time Samba gave me fits. It found the network OK, and let me designate a mount point, but would freeze every time when I tried to mount the drive.
I finally uninstalled everything....Samba AND LinNeighborhood.
...then I reinstalled it.
...same thing happened.
I must have went through this process of uninstalling & reinstalling 3-4 times. I even made sure that I deleted the files & directories the last time I did this.
...no matter, when I installed it again & gave it the correct information, it just froze up again.
I searched Google, and several forums for the answer. I never did see where anyone had this same identical problem; all the things I saw had to do with other situations; apparently this was something new.
The last time I turned the logs on in the Mandrake Control Center, and saw that it was issuing the commands correctly, but it would then freeze.
I decided to issue the same command in a terminal & see what happened.
I saw something curious....it came back asking me for the password...and without a CR it just stayed there.
You see, since this is on a home network that I control, I -DON'T- have a password for it for me to get in...just my username. I may change that soon. :)
I wondered how I was going to fix this. I considered redoing the Windows machine & giving me a password so that I could answer the question...but decided to try something else first.
When Samba asks for the UserID, Password, and Network Name, I placed the cursor in the password field and hit the spacebar one time, then tabbed down to the Network Name field & entered that.
It worked flawlessly then...all I had to do is enter -SOMETHING- in the password field.
This is apparently a bug...but I figured out how to get around it.
I don't know why it worked before, and didn't this time....WHO KNOWS?...maybe in the time before the first & second install Samba was upgraded?
I really don't know, and don't care to look. All I know is that I got it working, and now I'll go on to the next thing.
In the meantime I'll keep my eyes open for comments somewhere about this; maybe even someone else having the same kind of problem. I am also going to report this to Mandrake -AND- Samba along with this message so they have some background.
So...there's one 12 hour ordeal of confusion where something didn't work, and it just took -WORKING THROUGH THE PROBLEM- to get it working.
Sometimes other people just aren't going to have an answer for you, and you are going to have to use your own troubleshooting techniques to figure it out & get it working.
The moral to this story is this: Just keep trying, and keep your eyes open for things that don't look right.
Use the logs...they can give you a lot of information.
I am quite sure that good Network Administrators learned this a long time ago.
It's taken a long time, and I still consider myself to be a Newbie, but Linux is just plain fun sometimes.
And, I say that with a smirk. :)
Now I just accept most difficulties as they come, and try to work through them without any screaming rants or paranoia about linux.
You know, the love/hate relationship that we won't admit but is there nonetheless. :)
I installed Mandrake 9.2 about a week or so ago, and Samba worked & got configured flawlessly.
For experimental reasons, after I had it installed all this time I reinstalled it a couple days ago.
This time Samba gave me fits. It found the network OK, and let me designate a mount point, but would freeze every time when I tried to mount the drive.
I finally uninstalled everything....Samba AND LinNeighborhood.
...then I reinstalled it.
...same thing happened.
I must have went through this process of uninstalling & reinstalling 3-4 times. I even made sure that I deleted the files & directories the last time I did this.
...no matter, when I installed it again & gave it the correct information, it just froze up again.
I searched Google, and several forums for the answer. I never did see where anyone had this same identical problem; all the things I saw had to do with other situations; apparently this was something new.
The last time I turned the logs on in the Mandrake Control Center, and saw that it was issuing the commands correctly, but it would then freeze.
I decided to issue the same command in a terminal & see what happened.
I saw something curious....it came back asking me for the password...and without a CR it just stayed there.
You see, since this is on a home network that I control, I -DON'T- have a password for it for me to get in...just my username. I may change that soon. :)
I wondered how I was going to fix this. I considered redoing the Windows machine & giving me a password so that I could answer the question...but decided to try something else first.
When Samba asks for the UserID, Password, and Network Name, I placed the cursor in the password field and hit the spacebar one time, then tabbed down to the Network Name field & entered that.
It worked flawlessly then...all I had to do is enter -SOMETHING- in the password field.
This is apparently a bug...but I figured out how to get around it.
I don't know why it worked before, and didn't this time....WHO KNOWS?...maybe in the time before the first & second install Samba was upgraded?
I really don't know, and don't care to look. All I know is that I got it working, and now I'll go on to the next thing.
In the meantime I'll keep my eyes open for comments somewhere about this; maybe even someone else having the same kind of problem. I am also going to report this to Mandrake -AND- Samba along with this message so they have some background.
So...there's one 12 hour ordeal of confusion where something didn't work, and it just took -WORKING THROUGH THE PROBLEM- to get it working.
Sometimes other people just aren't going to have an answer for you, and you are going to have to use your own troubleshooting techniques to figure it out & get it working.
The moral to this story is this: Just keep trying, and keep your eyes open for things that don't look right.
Use the logs...they can give you a lot of information.
I am quite sure that good Network Administrators learned this a long time ago.
It's taken a long time, and I still consider myself to be a Newbie, but Linux is just plain fun sometimes.
And, I say that with a smirk. :)