Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Try this, open your smb.conf and delete this line "encrypt passwords = yes" then save the file, restart the 2 daemons
in the console >>> service smb restart
Then goto win2k server refresh ur network neighborhood, wait at least a min then click your linux host name and see if u able to see the linux share, good luck
Nah, that wouldn't have worked. With Win NT, 2k, and XP, you need to have that line. I was thinking that might be the problem until hak posted his conf file... I'm stumped, hak. Sorry!
Chris
hak, Have you tried with an older version of samba? I had to do that once... Last year, I installed the most recent version, it gave me sh*t for days, I removed it and installed an older version and everything was cool. To this day I don't know what was wrong, but oh well!
Know wait a minute.
I've got a question for all those how spent this much time on it.
When I gave up on it ohh about the third time it drop signal from the W2k pro.
Fact is that if the windows machine is not on before the Linux machine it would not recognize the Samba share just cause me to reboot.
Know I faced this same problem with windows 95/98 to a Windows 2000 server. They would some times find the workgroup and other time have a spike or miss connection causing me to reboot the windows 95/98 machine.
Finally the question is that by reading the book I have hear called "Samba Unleashed" Some where in the reading I came acrosst the fact that all version prior to Samba 3.0 were not to be taken as a fully supported version. Because all version prior to this were to be for better lack of a word a beta. So this is a way for programmer to figure out what is wrong and fix it in all the releases leading up to Samba 3.0......
Know this book hear is about 2 years old and I have not looked at Samba's website to see if they support this program to run as a fully supported version. Or does Samba state it runs without flaws.
Last but not least I'm trying to infact find the reason why a windows machine infact falls to connect to a Windows 2k server.
No solution yet don't know if it is missing a good connection with the DHCP server because it is running to far away and needs a DHCP relay agent or is there to meany requests asked at one time to windows server and puts to much load on the server.
OK Hak try this, Last night I had a man help get mine setup using Samba 3.02b-- we worked on it for two hours before we got it.
One thing funny was that my iptables were conflicting with my router, we disabled the Iptables completely. Then restarted Samba.
Now I have a custom script I will be glad to share with you- butit only works with Samba3.
Be sure remove any and all previous version of Samba before attemping to install 3.
How I did it was /etc/samba
# rm -f samba
It was quick and very efficient.
[printers]
comment = All Printers
path = /var/spool/samba
guest ok = Yes
printable = Yes
browseable = No
[public]
comment = A public share for vendor docs, etc.
path = /usr/public
read only = No
create mask = 0755
force directory mode = 0755
guest ok = Yes
[temp]
comment = A place to drop off temporary files
path = /tmp
read only = No
create mask = 0755
force directory mode = 0755
guest ok = Yes
[docs]
comment = Main Document Share for important Corporate Documents
path = /doc
read only = No
create mask = 0755
force directory mode = 0755
guest ok = Yes
[homes]
comment = Home directories
valid users = %S
read only = No
create mask = 0755
browseable = No
[profiles]
comment = User Profiles (change path as needed)
path = /var/spool/profiles
read only = No
profile acls = Yes
Well I'll be fucking damned, after days of problems
I got it, guess what the problem was!
Aboslutely nothing, theres a incompatibility with my server configuration and samba. 3.02b Samba upgrade via webmin, and the shit starts working, HURRAH HURRAH
If we had dancing bananas i'd post a screen of them
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.