Indeed incorrect setup (of the iptables firewall, not of dns/dhcp/firestarter) but the problem is resolved now I've put original iptables policy configuration back.
Thanks for the help, Regards Otto On Wed, Dec 10, 2008 at 11:56 AM, L.P.H. van Belle <[EMAIL PROTECTED]> wrote: > this is a dns+dhcp issue what you windows is not resolving. > your setup is not corrrect. > > Im running firestarter on 4 debian servers here, all have also > samba running it and windows resolves without any problems. > > questions about this, email my on [EMAIL PROTECTED] > I can email you my setup if you want. > > Louis > > >>-----Oorspronkelijk bericht----- >>Van: [EMAIL PROTECTED] >>[mailto:[EMAIL PROTECTED] Namens >>Otto Krüse >>Verzonden: 2008-12-10 11:27 >>Aan: [EMAIL PROTECTED] >>CC: [email protected] >>Onderwerp: Re: [Samba] Windows can see Ubuntu netbios names >>but not access oreven ping >> >>Thanks for the feedback. I am wondering indeed then how the local >>master browser got wind of it.. >> >>I find out the cause and solution for the problem as well.. turned >>out to be a firewall issue. The system is running Firestarter but also >>Shorewall is installed. Now Shorewall is 'only' a utility to update >>iptables policies and I hadn't actually run it so I figured my >>iptables policy would have remained unchanged. But as it seems the >>installation of shorewall already created some iptables policies... I >>deleted them and set new policies to accept all (and let firestarter >>do the firewalling) and now my windows pc resolves the netbios name of >>the server again. Whoa! >> >>Interesting to note is that name resolving from other linux machines >>worked ok, e.g. wasn't affected by the iptables policies. Only windows >>machines weren't able to pass through iptables policies for name >>resolving. That's nasty I think, seems to me you would not expect this >>difference.... >> >>Regards Otto >> >> >>On Tue, Dec 9, 2008 at 10:09 PM, Volker Lendecke >><[EMAIL PROTECTED]> wrote: >>> On Tue, Dec 09, 2008 at 03:21:37PM +0100, Otto Krüse wrote: >>>> Here's the funny thing: when my I browse the local network on my >>>> windows machine I can see the server (called ubuntuserver1). So >>>> somehow my windows pc can resolve the name. But when I try to access >>>> it (by double clicking) windows complains it cannot find the name. >>>> Also ping ubuntuserver1 does not work. >>> >>> The fact that "ubuntuserver1" shows up in the list of >>> machines in your workgroup does not mean that you can "see" >>> it yourself. It means that your local master browser somehow >>> got wind of it. >>> >>> Volker >>> >>-- >>To unsubscribe from this list go to the following URL and read the >>instructions: https://lists.samba.org/mailman/listinfo/samba > > -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
