We have a windows XP/2000 network. A linux red hat 8.0
machine was connected to this network. I configured
samba on it successfully.
When i go to My network places on my windows XP
machine i can see the linux machine. When i double
click on it i am immediately given a user name and
password dialog box. Now initially on entering the
username and passwd i could connect to the shares
without any problem. The next day (without any changes
made to any machine except the loggin off on the
windows XP machine) when i tried to access the linux
shaer i could not do so.
I again had to enable the
users by running "smbpasswd -e <username>". That was
the first wierd thing.
Today (as well as yesterday) when i double click on the
Linux machine it says "\\LinuxTest not accesible"
which is the error msg got only when samba is not
running. When i check on the linux machine i see that
samba is running properly.
Now what am i suppoed to do? Samba seems to be working
properly. There is no explanation for this.
The same thing happened with me using putty on windows
XP. I was using it to connect to the Linux machine via
ssh for over 2 days and then suddenly i cannot
connect!!! Stange.
SSH and samba appear not to be working when accessing from windows. But they are actually running on the Linux machine.
I reinstalled openssh and still i am unable to
connect.
I just wish to ask this group if there is anything
else i can do or check before i plan to do a complete
reinstall of the linux machine. Where is the problem
from....the linux machine or windows machine? Can such
a thing happen suddenly?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
if it is a routed network is samba announcing itself to the wins server? and if so if the server is using dhcp (from a pool) the wrong ip might be in the wins database. So make sure the linux machine has a static ip like jlevie said, and make sure that ip is the one listed in the wins db (if you use wins).
Hi,
I do not have any firewall configured. The linux machine has a static IP addres right from the beginning. And as i had said before it was working fine. Until it suddenly stopped working altogether. I am 200 % sure that there was no configuration change done or anything that would affect any services. The only thing i was doing was...i had a putty connection to the linux machine and i was playing around with the addition, creation and manegement of samba users.
Check your smb.conf and see if it is configured to sync Linux passwords when a Samba password changes. The default configuration in RedHat enables that option, so you might have changed your Linux password when fiddling with the Samba passwords. Such a change could explain why you then could not login via putty as you were probably trying to use your old Linux passwd.
Business Accounts
Answer for Membership
by: jleviePosted on 2003-07-11 at 10:17:55ID: 8904389
Might it be a firewall issue? Does 'ipchains -L" or 'iptables -L' return anything other than "ACCEPT?"
Is the Linux box set up to use DHCP and if so did the IP of the system change recently (like since the last boot)? Services bind to the IP of the machine when they start (typically at boot) and if the IP changes while the service is running there'll be problems. The solution is to configure the server with a static IP or to configure the DHCP server to give a static reservation to the system.