Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
okay, I have been fighting this issue for days now, and I have googled every error message I can get my hands on. All to no avail.
here's the setup:
Debian box (sarge, 2.4.27 kernel picked since 2.6 kernels *do not* like promise 20265 ide controllers), no domain, smbd. 3 shared drives.
d1200:~# uname -a
Linux d1200 2.4.27-2-686 #1 Thu Jan 20 11:10:41 JST 2005 i686 GNU/Linux
d1200:~# smbd -V
add a network shared drive (right click my computer -> Map Network Drive... enter info, Reconnect at Logon, save password..)
The drive mounts. Reading/Writing all files, no problems. Fast access. All good. Never any problems. reboot, shares come back mounted properly with proper permissions and access.
add a network shared drive (right click, map, enter info, reconnect, save passwd...)
The drive mounts. Read/Write files just fine. Then within a couple minutes, I start getting errors from WindozeXP:
G:\ is not accessible
Logon Failure: unknown user name or bad password.
so, since windoze errors are the most useful errors ever. I turn to my smb logs. I find for each shared drive, the following pair of lines:
[2005/05/05 03:53:44, 1] smbd/service.c:make_connection_snum(642)
xp1700 (192.168.0.20) connect to service junk initially as user doug (uid=0, gid=1000) (pid 5731)
[2005/05/05 03:56:16, 1] smbd/service.c:close_cnum(830)
xp1700 (192.168.0.20) closed connection to service junk
the first line is basically when winxp sp2 boots. The second message is a few minutes later, when the share decides to stop working. This is all the logs show.
So why is sp2 closing the connection, when sp1 (or no service pack) doesn't?
As for my sp2 configuration, I am on an internal network, and as such, I completely disable windows firewall in sp2. As for the sp1 configuration, it is completely up to date with windows update patches. It is only missing the actual sp2.
for kicks, I tried accessing one of the shared drives from a win2k server machine. It can access the drive with proper permissions no problem... and it doesn't time out.