Samba randomly doesn't connect to local server

Bug #187971 reported by Václav Čermák on 2008-02-01
2
Affects Status Importance Assigned to Milestone
samba (Ubuntu)
Undecided
Unassigned

Bug Description

I'm using Ubuntu 7.10 for the office work. All our data are stored on local server (also in the office). I had problem connecting to the server. Or actually I could connect but one day I could open files and edit and other I couldn't. Recently I've discovered that I have to unplug my laptop from the network and connect it during or after login. Then it works just fine.
Here is my version of Samba:
ii samba 3.0.26a-1ubuntu2.3 a LanManager-like file and printer server for Unix
I'm no geek so I just try to describe the problem in non-tech words.

There are a large number of possibilities. I recently reconfigured samba for
my home network in a manner which seems to drive many people nuts. But I
live behind a gateway router and I know my Windows box is clean and I choose
to live dangerously within the confines of my own home and the reach of my
two open wireless aps.

http://ls.net/software/crossplatform/samba

On 2/3/08, Stephan Klein <email address hidden> wrote:
>
> ** Changed in: samba (Ubuntu)
> Sourcepackagename: None => samba
>
> --
> Samba randomly doesn't connect to local server
> https://bugs.launchpad.net/bugs/187971
> You received this bug notification because you are a member of Ubuntu
> Server Team, which is a bug contact for samba in ubuntu.
>

Chuck Short (zulcss) wrote :

Can you please attach the output of the dmesg command to this bug report. This sounds more like a network problem.

Thanks
chuck

Changed in samba:
status: New → Incomplete
Václav Čermák (kingskid) wrote :

Sorry, I'm no geek. if you provide with exact command to obtain the report I
can do it.
Btw, if I plug the network cable into my laptop right after login I have no
problem using network and edit files on server.

Vaclav

2008/2/21, Chuck Short <email address hidden>:
>
> Can you please attach the output of the dmesg command to this bug
> report. This sounds more like a network problem.
>
> Thanks
> chuck
>
> ** Changed in: samba (Ubuntu)
> Status: New => Incomplete
>
>
> --
> Samba randomly doesn't connect to local server
> https://bugs.launchpad.net/bugs/187971
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Chuck Short (zulcss) wrote :

Sure run the following command from the commandline:

dmesg > dmesg.txt

And attach the file dmesg.txt.

Thanks
chuck

Václav Čermák (kingskid) wrote :
Download full text (24.0 KiB)

Attached.

Vaclav

2008/2/21, Chuck Short <email address hidden>:
>
> Sure run the following command from the commandline:
>
> dmesg > dmesg.txt
>
> And attach the file dmesg.txt.
>
> Thanks
>
> chuck
>
>
> --
> Samba randomly doesn't connect to local server
> https://bugs.launchpad.net/bugs/187971
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[ 0.000000] Linux version 2.6.22-14-generic (buildd@terranova) (gcc version 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)) #1 SMP Tue Feb 12 07:42:25 UTC 2008 (Ubuntu 2.6.22-14.52-generic)
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
[ 0.000000] BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 000000003efd0000 (usable)
[ 0.000000] BIOS-e820: 000000003efd0000 - 000000003efde000 (ACPI data)
[ 0.000000] BIOS-e820: 000000003efde000 - 000000003f000000 (ACPI NVS)
[ 0.000000] BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
[ 0.000000] BIOS-e820: 00000000fed13000 - 00000000fed1a000 (reserved)
[ 0.000000] BIOS-e820: 00000000fed1c000 - 00000000fed20000 (reserved)
[ 0.000000] BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
[ 0.000000] 111MB HIGHMEM available.
[ 0.000000] 896MB LOWMEM available.
[ 0.000000] found SMP MP-table at 000ff780
[ 0.000000] Entering add_active_range(0, 0, 258000) 0 entries of 256 used
[ 0.000000] Zone PFN ranges:
[ 0.000000] DMA 0 -> 4096
[ 0.000000] Normal 4096 -> 229376
[ 0.000000] HighMem 229376 -> 258000
[ 0.000000] early_node_map[1] active PFN ranges
[ 0.000000] 0: 0 -> 258000
[ 0.000000] On node 0 totalpages: 258000
[ 0.000000] DMA zone: 32 pages used for memmap
[ 0.000000] DMA zone: 0 pages reserved
[ 0.000000] DMA zone: 4064 pages, LIFO batch:0
[ 0.000000] Normal zone: 1760 pages used for memmap
[ 0.000000] Normal zone: 223520 pages, LIFO batch:31
[ 0.000000] HighMem zone: 223 pages used for memmap
[ 0.000000] HighMem zone: 28401 pages, LIFO batch:7
[ 0.000000] DMI 2.3 present.
[ 0.000000] ACPI: RSDP signature @ 0xC00F8BD0 checksum 0
[ 0.000000] ACPI: RSDP 000F8BD0, 0014 (r0 ACPIAM)
[ 0.000000] ACPI: RSDT 3EFD0000, 003C (r1 A M I OEMRSDT 11000524 MSFT 97)
[ 0.000000] ACPI: FACP 3EFD0200, 0084 (r2 A M I OEMFACP 11000524 MSFT 97)
[ 0.000000] ACPI: DSDT 3EFD0430, 3FC3 (r1 UW____ F24_____ 0 INTL 2002026)
[ 0.000000] ACPI: FACS 3EFDE000, 0040
[ 0.000000] ACPI: APIC 3EFD0390, 0054 (r1 A M I OEMAPIC 11000524 MSFT 97)
[ 0.000000] ACPI: MCFG 3EFD03F0, 003C (r1 A M I OEMMCFG 11000524 MSFT 97)
[ 0.000000] ACPI: OEMB 3EFDE040, 0046 (r1 A M I AMI_OEM 11000524 MSFT 97)
[ 0.000000] ACPI: MCFG 3EFD4400, 003C (r1 A M I OEMMCFG 11000524 MSFT 97)
[ 0.000000] ACPI: SSDT 3EFD4440, 03E7 (r1 AMI0 CPU1PM 1 INTL 2002026)
[ 0.000000] ACPI: PM-Timer IO Port: 0x808
[ 0.000000] ACPI:...

After 171 days of being expired, I'm going to assume that this bug has been fixed. Most likely in the hardware networking. Feel free to set the status back to New if it is still an issue.

Changed in samba:
status: Incomplete → Fix Released

LinkedIn
------------

Bug,

I'd like to add you to my professional network on LinkedIn.

- Jim

Jim Tarvid
Internet Engineer at LSNet
Johnson City, Tennessee Area

Confirm that you know Jim Tarvid
https://www.linkedin.com/e/-z3o2df-goaoxnlg-5g/isd/3040027802/EzLdkpvu/

--
(c) 2011, LinkedIn Corporation

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments