Networking Forums

Networking Forums > Computer Networking > Linux Networking > Samba 3.0.x vs Wind2K3 = "no network found"

Reply
Thread Tools Display Modes

Samba 3.0.x vs Wind2K3 = "no network found"

 
 
Lawrence DčOliveiro
Guest
Posts: n/a

 
      07-25-2005, 04:49 AM
I recently upgraded the main departmental server of a client of mine to
SuSE Linux 9.3, which came with Samba version 3.0.12-5. Previously it
would have been running some 2.x version of Samba. After this, users on
machines running Windows 2003 Server could no longer mount their shares
on the Linux box.

The message displayed on the Windows was "The drive could not be mapped
because no network was found". On the Samba side, the log file messages
were like

[2005/07/22 17:24:31, 0] lib/util_sock.c:get_peer_addr(1150)
getpeername failed. Error was Transport endpoint is not connected

XP users were still fine. (Don't ask me why users had to use Wind2003 as
a client--something to do with terminal server access.)

I tried the SuSE update to Samba 3.0.13-1.1, and also pulled down the
latest official 3.0.14a release from samba.org and built and installed
that, but nothing helped. Finally I downloaded 2.2.9, being the last
release of 2.x, and after installing that, all was right again.

Has anyone else encountered something similar?
 
Reply With Quote
 
 
 
 
Walter Mautner
Guest
Posts: n/a

 
      07-25-2005, 10:36 AM
Lawrence DčOliveiro wrote:

> I recently upgraded the main departmental server of a client of mine to
> SuSE Linux 9.3, which came with Samba version 3.0.12-5. Previously it
> would have been running some 2.x version of Samba. After this, users on
> machines running Windows 2003 Server could no longer mount their shares
> on the Linux box.
>
> The message displayed on the Windows was "The drive could not be mapped
> because no network was found". On the Samba side, the log file messages
> were like
>
> [2005/07/22 17:24:31, 0] lib/util_sock.c:get_peer_addr(1150)
> getpeername failed. Error was Transport endpoint is not connected
>
> XP users were still fine. (Don't ask me why users had to use Wind2003 as
> a client--something to do with terminal server access.)
>
> I tried the SuSE update to Samba 3.0.13-1.1, and also pulled down the
> latest official 3.0.14a release from samba.org and built and installed
> that, but nothing helped. Finally I downloaded 2.2.9, being the last
> release of 2.x, and after installing that, all was right again.
>

There have been some defaults changing in smb.conf from 2.x to 3.x.
I would suggest taking this to a dedicated samba group
(comp.os.linux.networking.samba as an example) and also posting the global
part of your smb.conf, together with a snippet of your logfile (%m.log)
from a 2k3 box trying to access the server when log level is something like
3-5.

--
Longhorn error#4711: TCPA / NGSCP VIOLATION: Microsoft optical mouse
detected penguin patterns on mousepad. Partition scan in progress
*to*remove*offending*incompatible*products.**Reactivate*MS*software.
Linux woodpecker.homnet.at 2.6.12-mm2[LinuxCounter#295241,ICQ#4918962]
 
Reply With Quote
 
Lawrence DčOliveiro
Guest
Posts: n/a

 
      07-26-2005, 05:28 AM
In article <furer2-(E-Mail Removed)>,
Walter Mautner <(E-Mail Removed)> wrote:

>There have been some defaults changing in smb.conf from 2.x to 3.x.


I actually copied across the same smb.conf I had been using with 2.x to
3.x.

>I would suggest taking this to a dedicated samba group


Yeah, I might try that next.
 
Reply With Quote
 
Lawrence DčOliveiro
Guest
Posts: n/a

 
      07-27-2005, 07:48 AM
In article <furer2-(E-Mail Removed)>,
Walter Mautner <(E-Mail Removed)> wrote:

>I would suggest taking this to a dedicated samba group
>(comp.os.linux.networking.samba as an example) ...


Except I can't find any such group.
 
Reply With Quote
 
Walter Mautner
Guest
Posts: n/a

 
      07-27-2005, 06:40 PM
Lawrence DčOliveiro wrote:

> In article <furer2-(E-Mail Removed)>,
> Walter Mautner <(E-Mail Removed)> wrote:
>
>>I would suggest taking this to a dedicated samba group
>>(comp.os.linux.networking.samba as an example) ...

>
> Except I can't find any such group.


Mmhm, sorry, I use the "de.*" and thought there should also exist a
international group. Sorry.
Now I only find comp.protocols.smb (looks almost dead these days) and
linux.samba, which is actually a mirror of the samba mailinglist and
moderated, so you can't post a quick question there.
Anyone else?

--
Longhorn error#4711: TCPA / NGSCP VIOLATION: Microsoft optical mouse
detected penguin patterns on mousepad. Partition scan in progress
*to*remove*offending*incompatible*products.**Reactivate*MS*software.
Linux woodpecker.homnet.at 2.6.12-mm2[LinuxCounter#295241,ICQ#4918962]
 
Reply With Quote
 
Walter Mautner
Guest
Posts: n/a

 
      07-28-2005, 07:34 PM
Lawrence DčOliveiro wrote:

> In article <furer2-(E-Mail Removed)>,
> Walter Mautner <(E-Mail Removed)> wrote:
>
>>I would suggest taking this to a dedicated samba group
>>(comp.os.linux.networking.samba as an example) ...

>
> Except I can't find any such group.


Mmhm, sorry, I use the "de.*" and thought there should also exist a
international group. Sorry.
Now I only find comp.protocols.smb (looks almost dead these days) and
linux.samba, which is actually a mirror of the samba mailinglist and
moderated, so you can't post a quick question there.
Anyone else?

--
Longhorn error#4711: TCPA / NGSCP VIOLATION: Microsoft optical mouse
detected penguin patterns on mousepad. Partition scan in progress
*to*remove*offending*incompatible*products.**Reactivate*MS*software.
Linux woodpecker.homnet.at 2.6.12-mm2[LinuxCounter#295241,ICQ#4918962]
 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

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 On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Computers getting "The network path was not found" message LJH Windows Networking 10 04-17-2009 05:10 PM
"drive could not be mapped because no network was found" Erasmo Acosta Linux Networking 3 05-24-2008 08:29 AM
"Network Path Not Found" in Accessing Shared Docs catjammies Wireless Networks 0 11-29-2005 04:53 PM
WINS error: " The network path not found" James Windows Networking 1 11-17-2005 03:36 PM
AttributeType not found: "gidNumber" errormessage - Openldap + samba + Suse 9.2 Andreas Bauer Linux Networking 0 06-03-2005 10:38 AM



1 2 3 4 5 6 7 8 9 10 11