Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Access standalone network drive from Linux (Fedora 7)?
#1

I have a standalone drive that I'm trying to access from Linux (Fedora 7).

 

In Windows, I access this drive by entering "\\netdrive\public" in the Explorer address bar.

 

I'm new to Linux, but I think I would need to mount this drive using smbmount or mount -smb or something similar; recent googling seems to indicate that smbmnt is no longer in Fedora, so I need to use mount -t cifs instead.

 

I've tried various parameters with mount -cifs. I think I want to do something like:

 



Code:
mount -cifs //netdrive/public /mnt/netdrive/public -o username=myname




 

but I get:

mount error 111 = Connection refused.


Can someone provide some help in configuring this? I'm not sure if the problem is with my use of mount -cifs, or if I'm even seeing the drive on the network.

 

Thanks in advance!

Reply
#2

sounds like a firewall is enabled on the other box

 

have you checked the tips and tricks section here ? there's very specific howtos for samba etc

 

cheers

anyweb

Reply
#3
Yeah the most obvious thing would be a firewall or that the username/password wasn't valid.
Reply
#4

Thanks for the suggestions.

 

There is no firewall on the other box -- it is just a standalone network drive.

 

I'm not sure what to specify for the username and password -- when I connect to this drive from Windows, I don't have to login or specify a password -- just enter the address in Explorer and it connects.

 

I temporarily disabled the SPI firewall on the router and the Linux firewall, but I still get this error.

 

I also confirmed that I can ping the IP address of the drive.

 

But I'm still getting mount error 111 = Connection refused

 

I've looked through the tips and tricks, but I don't see anything that appears to address this. Any suggestions?

Reply
#5

are you sure you have samba and all it's tools installed ?

 

i had a similar issue recently with Fedora 8 and (slaps self) it turned out that the reason i couldn't browse my windows network was because i was missing some samba tools

 



Code:
yum search samba




 

should give you a good idea

 

cheers

anyweb

Reply
#6
Explain how the network drive is shared, that might assist us with how it will works. Secondly try using the IP rather than the computer name (//IP/public).
Reply
#7

Quote:are you sure you have samba and all it's tools installed ? 

i had a similar issue recently with Fedora 8 and (slaps self) it turned out that the reason i couldn't browse my windows network was because i was missing some samba tools

 



Code:
yum search samba

<div>


 

should give you a good idea

 

cheers

anyweb

</div>
 

Thanks, anyweb!

 

I'm definitely a noob, so I'm not quire sure what I'm looking at. I got:

 

[root@localhost ~]# yum search samba

fedora 100% |=========================| 2.1 kB 00:00

updates 100% |=========================| 2.3 kB 00:00

primary.sqlite.bz2 100% |=========================| 2.3 MB 00:51

adobe-linux-i386 100% |=========================| 951 B 00:00

samba.i386 : The Samba Suite of programs

smb4k.i386 : The SMB/CIFS Share Browser for KDE

smbldap-tools.noarch : User and group administration tools for Samba/OpenLDAP

system-config-samba.noarch : Samba server configuration tool

smb4k.i386 : The SMB/CIFS Share Browser for KDE

dbench.i386 : Filesystem load benchmarking tool

samba-client.i386 : Samba client programs

amanda.i386 : A network-capable tape backup solution.

snort.i386 : Intrusion detection system

samba-swat.i386 : The Samba SMB server Web configuration program

samba-client.i386 : Samba client programs

samba-common.i386 : Files used by both Samba servers and clients

python-smbpasswd.i386 : Python SMB Password Hash Generator Module

samba.i386 : The Samba Suite of programs

snort.i386 : Intrusion detection system

libsmbclient.i386 : The SMB client library

libsmbclient.i386 : The SMB client library

system-config-samba.noarch : Samba server configuration tool

samba.i386 : The Samba Suite of programs

libsmbclient-devel.i386 : Developer tools for the SMB client library

mod_auth_ntlm_winbind.i386 : NTLM authentication for the Apache web server using winbind daemon

samba-common.i386 : Files used by both Samba servers and clients

fuse-smb.i386 : FUSE-Filesystem to fast and easy access remote resources via SMB

ccache.i386 : C/C++ compiler cache

samba-client.i386 : Samba client programs

amanda.i386 : A network-capable tape backup solution.

ccache.i386 : C/C++ compiler cache

nautilus-share.i386 : Easy sharing folder via Samba (CIFS protocol)

samba-doc.i386 : Documentation for the Samba suite

pam_mount.i386 : A PAM module that can mount volumes for a user session

samba-common.i386 : Files used by both Samba servers and clients

rzip.i386 : A large-file compression program

samba-swat.i386 : The Samba SMB server Web configuration program

perl-Crypt-SmbHash.noarch : Pure-perl Lanman and NT MD4 hash functions

libsmbclient-devel.i386 : Developer tools for the SMB client library

samba-doc.i386 : Documentation for the Samba suite

php-pear-File-SMBPasswd.noarch : Class for managing SAMBA style password files

libsmbclient.i386 : The SMB client library

libntlm.i386 : NTLM authentication library

 

I'm not quite sure what that means. Do you see anything that is missing? Is there something I have missed? Anything I need to configure to get samba to work?

Backing up a bit, I tried browsing the Windows Network, but it is showing up empty. I guess I need to figure out how to see other computers (and shared directories/drives) on the network before I'll succeed at mounting the drive...

Reply
#8

Quote:Backing up a bit, I tried browsing the Windows Network, but it is showing up empty.
 

i dont have the box to hand, but try this as root

 



Code:
yum install samba-client.i386 -y




 

then

 



Code:
yum install samba.i386 -y




 

does browsing the windows network show any windows computers now ?

Reply
#9

Thanks for hanging in there with me! I still don't see any computers when I browse the network. :-(

 

It looks like both packages were already installed:

 

[root@localhost ~]# yum install samba-client.i386 -y

fedora 100% |=========================| 2.1 kB 00:00

primary.sqlite.bz2 100% |=========================| 3.8 MB 00:06

updates 100% |=========================| 2.3 kB 00:00

adobe-linux-i386 100% |=========================| 951 B 00:00

Setting up Install Process

Parsing package install arguments

Package samba-client - 3.0.28-0.fc7.i386 is already installed.

Nothing to do

[root@localhost ~]# yum install samba.i386 -y

Setting up Install Process

Parsing package install arguments

Package samba - 3.0.28-0.fc7.i386 is already installed.

Nothing to do

[root@localhost ~]#

 

Here's another data point. I'm not quite sure what this means, but it seems to be the first time I've successfully communicated with the drive:

 

root@localhost ~]# smbclient -L 192.168.2.4/Public

Password:

Domain=[ȇ] OS=[] Server=[���]

 

Sharename Type Comment

--------- ---- -------

PUBLIC Disk

IPC$ IPC

Domain=[ȇ] OS=[] Server=[���]

 

Server Comment

--------- -------

 

Workgroup Master

--------- -------

 

Any ideas?

Reply
#10

ok a quick look on my Fedora 8 box (this one)

 

and I can see the following smb packages are installed

 

Quote:pam_smbgnome-vfs2-smb

libsmbclient

samba-client

samba
 

so if you are missing any of the above please install them and try again

 

cheers

anyweb

Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)