LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Fedora
User Name
Password
Fedora This forum is for the discussion of the Fedora Project.

Notices


Reply
  Search this Thread
Old 05-12-2004, 10:20 AM   #16
motub
Senior Member
 
Registered: Sep 2003
Location: The Netherlands
Distribution: Gentoo (main); SuSE 9.3 (fallback)
Posts: 1,607

Rep: Reputation: 46

Doing a Google search for ls "I/O error" linux samba reveals that this is/was a big problem with Samba, but the issue seems to revolve around Samba 2.06 (and I didn't see any solutions, just a lot of people reporting the problem-- but then I didn't go through all 10 pages of hits, either). What version of Samba are you using?
 
Old 05-12-2004, 03:37 PM   #17
BlandoCal
Member
 
Registered: Sep 2003
Location: Ames, IA
Distribution: Fedora Core 3
Posts: 92

Rep: Reputation: 15
I believe there may be a bug w/ fedora 1 that won't let you browse MS shares through Network Servers if the firewall is on, I read through the posts quickly and I might have missed it if someone else said it or if you tried it, but try and stop your firewall if its up:

service iptables stop

then try opening network servers
 
Old 05-12-2004, 05:57 PM   #18
thanquol
Member
 
Registered: Aug 2003
Location: Northern Sweden
Distribution: Fedora Core 3
Posts: 52

Rep: Reputation: 15
I suspected the fw, so I turned it of a couple of days ago

I'm running FC2 with SE enabled, so I'm running version 3.0.3-5 of smb
 
Old 05-12-2004, 06:00 PM   #19
motub
Senior Member
 
Registered: Sep 2003
Location: The Netherlands
Distribution: Gentoo (main); SuSE 9.3 (fallback)
Posts: 1,607

Rep: Reputation: 46
OK, but what about the Windows firewall? Is port... 139, I think it is... closed on the Win box?
 
Old 05-13-2004, 03:28 AM   #20
thanquol
Member
 
Registered: Aug 2003
Location: Northern Sweden
Distribution: Fedora Core 3
Posts: 52

Rep: Reputation: 15
I actually dont know...

But the following thing works out fine (with following result):

# smbclient //CIFSservername/sharename --user username%password --workgroup domainname -L

Domain=[DOMAINNAME] OS=[Windows 5.0] Server=[Windows 2000 LAN Manager]
smb: \>


at this stage I'm connected to the server, and when I type the 'ls' command I can read the content of the share:

smb: \> ls
. D 0 Fri Apr 30 13:42:29 2004
.. D 0 Fri Apr 30 13:42:29 2004
.Trash-thanquol D 0 Thu Mar 4 15:55:38 2004
Absolut D 0 Thu Mar 4 15:35:25 2004
Arkive file OutLook D 0 Sat Dec 6 19:39:37 2003
BACKUP D 0 Sat Dec 6 19:39:44 2003
dok DR 0 Mon Apr 5 16:21:09 2004
download D 0 Wed Apr 21 12:09:01 2004
gammalt D 0 Tue Feb 17 14:56:29 2004
hem D 0 Thu Mar 18 17:40:41 2004
LOGFILES D 0 Sat Dec 6 19:44:59 2003
outlook.pst 32768 Mon Apr 5 16:23:22 2004
PC D 0 Mon May 10 14:43:14 2004
Pivot D 0 Sat Dec 6 19:45:21 2003
PUTTY.RND 600 Mon Apr 5 17:43:48 2004
TEMP D 0 Sat Jan 17 02:08:39 2004

51199 blocks of size 4194304. 11892 blocks available


I dont know exactly, but according to the man pages for smbclient and smbmount, both uses port 139 when making connections to the server. I think that that is not the problem then?

I'm very grateful for all help that you give to me!

Last edited by thanquol; 05-13-2004 at 04:34 AM.
 
Old 05-13-2004, 04:48 AM   #21
motub
Senior Member
 
Registered: Sep 2003
Location: The Netherlands
Distribution: Gentoo (main); SuSE 9.3 (fallback)
Posts: 1,607

Rep: Reputation: 46
So, what you're saying is that if you connect to the server and then to the share as two separate operations it works and you can list the share, but if you connect to both the server and the share in the initial operation, you cannot.

Actually, this makes sense, given that you are getting a timeout error.

Apparently doing both connections in one go goes too quickly for the authentication procedure on the server (or something of the sort; I am decidedly not a network guru).

I don't know how to solve that offhand (is there some kind of 'wait' or 'pause' function available to this command?), but at least (I think) we have an idea of where to start looking for answers (how to slow down your request, or speed up the server's acceptance of that request).

As off the wall as it sounds, could this be a network issue? Is your NIC (both the one in your PC and the one in the other box) correctly set up (using Full-duplex, full speed, etc)?
 
Old 05-13-2004, 09:54 AM   #22
thanquol
Member
 
Registered: Aug 2003
Location: Northern Sweden
Distribution: Fedora Core 3
Posts: 52

Rep: Reputation: 15
Hmmm... no, not exactly.

With smbclient I do connect to the server and the share exactly the same way as I do when I run smbmount.

The difference is that when I connect with smbclient (to a share on the server), I get a specific prompt smb>
when I use that prompt, then I can see all the files thats on my share.

Within the smbclient command, I do have some commands, and they are similar to ftp.

Mouonting the share with smbmount, goes perfectly, the problem is when I try to read the share, for example with the 'ls' command, then I get the I/O-error after a timeout.

I do not think that there are any network issues on the server or on my PC, because it used to work with FC1.
 
Old 05-13-2004, 11:02 AM   #23
motub
Senior Member
 
Registered: Sep 2003
Location: The Netherlands
Distribution: Gentoo (main); SuSE 9.3 (fallback)
Posts: 1,607

Rep: Reputation: 46
Sorry, I misunderstood.

According to man smbmount:
Quote:
One smbfs bug is important enough to mention here, even if it is a bit
misplaced:


<B7> Mounts sometimes stop working. This is usually caused by smbmount
terminating. Since smbfs needs smbmount to reconnect when the server
disconnects, the mount will eventually go dead. An umount/mount nor-
mally fixes this. At least 2 ways to trigger this bug are known.
This appears to be the same bug that I got reference to in my previous Google search, and the fact that the end of my man page says:
Quote:
The conversion of this manpage for Samba 2.2 was performed by Gerald
Carter. The conversion to DocBook XML 4.2 for Samba 3.0 was done by
Alexander Bokovoy.
suggests that I can't even claim that maybe the bug was closed with Samba 3 and these are old docs or something.

Now clearly, the idea that "mounts may sometimes stop working" is not quite the same as "mounts stop working immediately upon connection", which seems to be what is happening to you, and also may be related specifically to Fedora.

While you're checking bug reports for both Samba and Fedora, perhaps you'd want to consider an alternative to using smbmount to connect to this share. NFS, perhaps, as suggested by man smbmount? Perhaps not using "ls" in a terminal, but (since the share is mounted) reading it normally in a file manager, maybe midnight commander since you're in a terminal anyway? Possibly (again) using a program such as LinNeighborhood to mount the shares rather than doing it yourself? I always wondered why you had to tell LN specifically what version of smbmount you were using in the Preferences, and why there was a specific choice between "version=2.05" and "version>=2.06", when, normally, how much difference could there be in a tenth-point release? But since Samba/smbmount 2.06 seems to be where this problem began, I guess maybe now I know why. Since this appears to be such a longstanding recurring issue, I would think that helper programs like LinNeighborhood might have developed some workarounds (some sort of "keep-alive" mechanism, perhaps) to avoid the problem. And this might also explain why Nautilus-smb doesn't work so well, and why it seems to be available only as an extra package rather than part of general GNOME installs the past few revisions.

Investigating alternatives is worth a shot, anyway; the situation can't get much less congenial than it is now.
 
Old 05-20-2004, 10:49 AM   #24
stain6
LQ Newbie
 
Registered: Feb 2002
Distribution: RedHat 7.2
Posts: 3

Rep: Reputation: 0
Hello,

I got something similar! Yes I can mount win computers with samba using mount and I even included one in fstab. It works great!

What it is not working is browsing "network neighborhood" with nautilus using "browse network"! It shows, that something is going on, status bar shows the correct number of LAN computers, but few seconds after that it stops and status line counts 0 computers found. This is nautilus issue, since network browsing works with all other smb GUI's out there.

Using command line never fails... and I can't find this bug to be reported. Anyone?

--------------
FC 2 P-500MHZ 384MB RAM

Last edited by stain6; 05-20-2004 at 10:51 AM.
 
Old 05-20-2004, 12:08 PM   #25
BlandoCal
Member
 
Registered: Sep 2003
Location: Ames, IA
Distribution: Fedora Core 3
Posts: 92

Rep: Reputation: 15
I'm experiencing this same problem with FC2:
(hangs when I try to list smb mounts ).
Thing is it worked fine yesterday. I'm wondering if maybe I changed something or whatever?

Heres the 'story'

I noticed with FC2 Test3 that smb mounts wouldn't 'work':
- it would let me mount them but would hang if I tried to go to the share or 'ls' anything in the share. (which seems to be the problem here)

After I installed the final FC2 it worked like a charm
- I could mount smb shares and 'ls' the contents and even run programs in them (this was yesterday)

Now today when I try to do this it hangs again. Something must have changed?

Other things:
- At first this morning, when I would view the 'Windows Network' through Nautilus (smb:///) it would show all the computers on our network,
- but when trying to connect to a windows computer it would NOT as for a login (like it used to in FC1) but because of this it would say permission denied (is there a place where you can set the login samba uses?)
- when trying to connect to other Linux computers, worked fine (still no login)
- I messed around with my smb.conf file and now nothing shows up in the 'Windows Network' (smb:///), so I thought I undid everything, but still nothing (good reason to back up .conf(s), oops)

I just thought I'd add this encase it helps anyone figure out this problem, or if they have an idea about what I changed.....

Mark
 
Old 05-20-2004, 12:35 PM   #26
BlandoCal
Member
 
Registered: Sep 2003
Location: Ames, IA
Distribution: Fedora Core 3
Posts: 92

Rep: Reputation: 15
A few more things:

- I can connect to windows shares using smbclient through the command
- if i open nautilus and type: smb://workgroup
it will bring me to our workgroup, but all the computers are represented by 'blank' files (that is file with the gnome foot icon in the center), if I click one of the 'computers' it says:

Cannot open ComputerName

The filename "ComputerName" indicates that this file is of type "(null)". The contents of the file indicate that the file is of type "Samba share". If you open this file, the file might present a security risk to your system.

Do not open the file unless you created the file yourself, or received the file from a trusted source. To open the file, rename the file to the correct extension for "Samba share", then open the file normally. Alternatively, use the Open With menu to choose a specific application for the file.

So its like nautilus isn't running it correctly?????

Any Ideas
 
Old 05-21-2004, 04:22 AM   #27
stain6
LQ Newbie
 
Registered: Feb 2002
Distribution: RedHat 7.2
Posts: 3

Rep: Reputation: 0
I confirm...
I also get "blank" document! Is this a bug or ARE ONLY 3 PEOPLE facing this problems?
 
Old 05-21-2004, 01:30 PM   #28
brimlar
LQ Newbie
 
Registered: Oct 2003
Posts: 2

Rep: Reputation: 0
I was using Fedora Core 1 in a corporate environment, and I could use Nautilus or Konqueror (Konqueror was faster) to browse computers in our domain via Samba (smb://). However, since I upgraded to Fedora Core 2, I am no longer able to browse computers in our domain, and my samba settings have remained the same.

If I connect to a server directly (knowing its name), I am able to mount it on my desktop without any problems whatsoever. (Upon double-clicking the icon for the server mount, it prompts me for my username, domain and password, and lets me through)

I re-enabled winbind (a post somewhere else informed me that the winbind service is apparently turned off by default in FC2), but this has changed nothing so far.

I am most perplexed.
 
Old 05-24-2004, 07:39 PM   #29
tspauld98
LQ Newbie
 
Registered: Aug 2001
Location: Boston, MA
Distribution: Fedora Core 2
Posts: 4

Rep: Reputation: 0
Bug Confirmed

Hi All,

Here's the deal with the Samba issue with Nautilus/GNOME in Fedora Core 2. It is a bug and a bad one, IMHO. If you mount a volume using the smbfs driver, any process, including umount -f, that accesses the volume hangs. This means that you have to do a hard reset of your computer after a reboot because init level 6 can't unmount your mounted samba volume. For more details, see the following bug report:

http://bugzilla.redhat.com/bugzilla/....cgi?id=123895

The good news is that there is a workaround. If you mount the samba volume before you start GNOME, i.e. in a script in rc3.d or by booting into run level 3 and mounting the volume before starting X windows, the volume mounts fine and you can access it. Any subsequent volumes can be mounted once GNOME starts. It's only the initial volume that hangs things. Tomorrow, I'll be writing my run level 3 script and waiting for the bug fix.

Thanks,

tims
 
Old 05-26-2004, 04:27 AM   #30
adepali
LQ Newbie
 
Registered: May 2004
Posts: 1

Rep: Reputation: 0
I have the same problem. Just installed Fedora Core 2, and tried to mount a Windows share, //ektoras/users. I've setup my workgroup correctly, as WORKGROUP. First of all, I couldn't get FC to recognize ektoras, and smbmount failed with 'Couldn't connect to ektoras' error, until I added ektoras to /etc/hosts and mount worked fine. However when I try to do any action with the mounted dir, the application freezes. Ie, when i use a terminal and try an ls, the terminal freezes, when i click on the share icon on the desktop, the entire desktop freezes etc.

When I try to reboot the machine, I get a bunch of 'smb_add_request timed out!' and '/mnt/ektoras: Input/output error' messages before it shuts down.

This is final fedora core 2 release, and i'm using samba-3.0.3-5

Mounting this windows share works just fine from my redhat 9 box.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Can't install "glibmm" library. "configure" script can't find "sigc++-2.0&q kornerr Linux - General 4 05-10-2005 02:32 PM
Couldn't display "SMB:///" , No host "(Null)" could been Found?????? munkey Linux - Newbie 3 05-03-2004 04:30 PM
Couldn't display "SMB:///" , No host "(Null)" could been Found?????? help munkey Fedora 6 04-30-2004 06:04 PM
"X-MS" cant open because "x-Multimedia System" cant access files at "smb&qu ponchy5 Linux - Networking 0 03-29-2004 11:18 PM
i just finished typing "./configure" and "make" in mplayer directory... kublador Linux - General 4 02-22-2003 03:12 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Fedora

All times are GMT -5. The time now is 06:42 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration