Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
We have a Suse linux server on our network (across the WAN), and need to mount Windows shares with it. I can mount shares just fine on windows boxes from my laptop (Slackware) on the local network. I come from a Slackware/Gentoo background, and am apparently not mounting correctly with Suse. This is my procedure:
mount -t smbfs //192.168.0.1/temp /mnt/windows 7822: session request to 192.168.0.1 failed (Called name not present)
7822: session request to 192 failed (Called name not present)
7822: session request to *SMBSERVER failed (Called name not present)
SMB connection failed
I glanced over the /etc/samba/smb.conf file and it appears ok. Any suggestions?
yes, fair enough. afaik samba doesn't actually resolve computer names by dns means, but instead broadcasts out and waits for the compuet to own up to being that machine. try just using the host name. of course, i might be completely wrong. that's been known a few times
hehe, already tried that. Mounting with hostname results in this:
tdb((null)): tdb_open_ex: could not open file //var/lib/samba/unexpected.tdb: No such file or directory
tdb((null)): tdb_open_ex: could not open file //var/lib/samba/unexpected.tdb: No such file or directory
tdb((null)): tdb_open_ex: could not open file //var/lib/samba/unexpected.tdb: No such file or directory
tdb((null)): tdb_open_ex: could not open file //var/lib/samba/unexpected.tdb: No such file or directory
tdb((null)): tdb_open_ex: could not open file //var/lib/samba/unexpected.tdb: No such file or directory
tdb((null)): tdb_open_ex: could not open file //var/lib/samba/unexpected.tdb: No such file or directory
tdb((null)): tdb_open_ex: could not open file //var/lib/samba/unexpected.tdb: No such file or directory
tdb((null)): tdb_open_ex: could not open file //var/lib/samba/unexpected.tdb: No such file or directory
tdb((null)): tdb_open_ex: could not open file //var/lib/samba/unexpected.tdb: No such file or directory
8126: Connection to windowsbox failed
SMB connection failed
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.