SAMBA Unseen!!!

David Comeau davitron at vl.videotron.ca
Sat Oct 20 13:41:06 GMT 2001


Although I can now see the server, I am still not able to connect to it. 
Looking at the /var/log/samba/log.smbd file, the following shows up:

open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error 
was Can't assign requested address

I seem to be making headway.

On 20 October, 2001 14:43, you wrote:
> Hi,
>
> I think that setting up your Samba machine as a WINS server would solve
> the problem. Add the following line to your smb.conf in the global
> section:
>
> wins support = yes
>
> Regards,
>
> Jan-Pieter van den Heuvel
> Piozum Computer & Webpagebuilding
>
> -----Oorspronkelijk bericht-----
> Van: samba-admin at lists.samba.org
> [mailto:samba-admin at lists.samba.org]Namens David Comeau
> Verzonden: vrijdag 19 oktober 2001 21:53
> Aan: samba at lists.samba.org
> Onderwerp: SAMBA Unseen!!!
>
>
> I've spent the last four days battling it out with samba and WinME. I'm
> hoping that someone
> may have some insight.
>
> Four machines altogether.
>
> 1) FreeBSD 4.4-RELEASE
> 2) Windows ME
> 3) Windows 98 SE
> 4) Windows 95a
>
> (the samba setup is exactly the same at another location, with the only
> difference being that
> there is only the windows ME machine and the freebsd machine)
>
> --TCP network--
> The network itself works beautifully. Every machine can ping itself and
> all the other machines.
> They can all ping outside the network, that is, the internet. Name
> resolution is working as it
> should. FTP, ssh (on the bsd machine), and every other service seems to
> be working as they
> should.
>
> --Windows network--
> Machines number 3 and 4 can see and connect/mount each other's shares.
> Machine number 2 cannot see the network , but can mount the shares on
> machines number 3 and 4.
> The machine cannot see nor connect/mount machine number 1.
> Machine number 1 can see and mount (through smbfs) all of the other
> machines, but not itself.
>
> Machine number 1 is setup w /ipfw and natd (using the default OPEN
> option), as well as samba 2.2.2
>
> Does anyone have any ideas or have seen this before? If you have, is
> there something I can do to
> fix this (other than get rid of Windows)?

-- 
===

Sincerely,
David Comeau




More information about the samba mailing list