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.
I have a WinXP Pro system networked to a Linux SUSE 9 with Samba. I have successfully connected the XP system to Samba with file and printer mappings for about the past year. After a few days, software I use to backup the XP system (in the background at 3:00 AM) to the Linux server will begin reporting that the drive is inaccessible. I can see the drive with Explorer and even browse the drive directories and folders. After doing this, the drive is accessible to the backup task. It will be OK for a few days before once again becoming inaccessible. I have tried to schedule a simple DOS BAT to list a directory on the drive prior to the backup task starting thinking I could reestablish the connection but this DOS task also fails with a like error. Any suggestions on what to look for in my Samba configuration or in Windows to keep this from happening?
Found in: file:/var/log/samba/log.nmbd
[2005/07/26 03:02:16, 0] nmbd/nmbd_namequery.c:query_name_response(112)
query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.4 for name NAGYFAMILY<1d>.
This response was from IP 192.168.1.101, reporting an IP address of 192.168.1.101.
I found messages in other logs that referenced printing issues and have not included them.
In the week since I made the change to the computer name, the share has remained available and there have been no failures during the nightly backup. Thanks for interpreting the message and providing a fix.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.