I've set up my Samba PDC to act as a WINS server, because I need remote access to it (through a VPN connection). I put "wins support = Yes" into the smb.conf file. As far as I know, WINS doesn't use a unique port number, so enabling the usual NetBIOS ports (137/udp, 138/udp, 139/tcp) on the firewall should be enough to make WINS work. I did this already. I tried to connect to a share on my PDC through a VPN connection. My VPN server properly sends the address of the WINS server, that's sure, I can see the correct address in the output of "ipconfig /all". smdb and nmdb are bound to the wildcard address to accept connections from ppp interfaces created on the fly. Everything seems to work correctly, but my clients cannot use NetBIOS names, when connecting to a share. Connecting to the server by its IP address works with no problem. I am creative, so I decided to disable WINS and use DNS instead. After that, name resolution worked wonderfully. But it's not that easy... by using DNS, my PDC is not able to resolve the netbios names of remote clients, because they don't register their names in DNS when connecting. Is there any way to use WINS on VPN clients? It seems, that Windows silently ignores my WINS server and only tries to resolve names with broadcasting, which is of course not possible through a PPP connection. Do you have any ideas? I use Samba 3.0.28a on my PDC and Windows XP Professional on my client.
On Fri, Jul 18, 2008 at 04:50:46PM +0200, kissg wrote:> I've set up my Samba PDC to act as a WINS server, because I need remote > access to it (through a VPN connection). I put "wins support = Yes" into the > smb.conf file. As far as I know, WINS doesn't use a unique port number, so > enabling the usual NetBIOS ports (137/udp, 138/udp, 139/tcp) on the firewall > should be enough to make WINS work. I did this already. > I tried to connect to a share on my PDC through a VPN connection. My VPN > server properly sends the address of the WINS server, that's sure, I can see > the correct address in the output of "ipconfig /all". smdb and nmdb are > bound to the wildcard address to accept connections from ppp interfaces > created on the fly. Everything seems to work correctly, but my clients > cannot use NetBIOS names, when connecting to a share. Connecting to the > server by its IP address works with no problem. > I am creative, so I decided to disable WINS and use DNS instead. After that, > name resolution worked wonderfully. > But it's not that easy... by using DNS, my PDC is not able to resolve the > netbios names of remote clients, because they don't register their names in > DNS when connecting. Is there any way to use WINS on VPN clients? It seems, > that Windows silently ignores my WINS server and only tries to resolve names > with broadcasting, which is of course not possible through a PPP connection. > Do you have any ideas?If I was you I would try to reproduce the problem without the VPN client active. If you connect the Windows client directly to the LAN it should make use of WINS correctly if configured to do so. You can check this with a sniffer, or if you have it available, use a routed LAN separate from the one where your PDC is located. If that works fine, then the VPN client software is very likely the one breaking WINS. Volker -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://lists.samba.org/archive/samba/attachments/20080718/dcf31954/attachment.bin
This is a big problem with samba 3.x because it's use NetBIOS for domain logon. DNS is not supported on samba 3.x because Samba 3.x working on NT.4 technology and its only support Netbios domain name. If you want to use DNS with Samba then you should go for Samba 4.0 it's base on Windows 2003 technology and working like Active Directory. I am also working on samba 4.x but still it in beta test not for production. $ cat ~/satish/url.txt????????????????????????????????????????????????????? http://www.linuxbug.org _____________________________________________________________________________________________________ --- On Fri, 18/7/08, kissg <mail.gery@gmail.com> wrote: From: kissg <mail.gery@gmail.com> Subject: [Samba] WINS name resolution doesn't work To: samba@lists.samba.org Date: Friday, 18 July, 2008, 8:20 PM I've set up my Samba PDC to act as a WINS server, because I need remote access to it (through a VPN connection). I put "wins support = Yes" into the smb.conf file. As far as I know, WINS doesn't use a unique port number, so enabling the usual NetBIOS ports (137/udp, 138/udp, 139/tcp) on the firewall should be enough to make WINS work. I did this already. I tried to connect to a share on my PDC through a VPN connection. My VPN server properly sends the address of the WINS server, that's sure, I can see the correct address in the output of "ipconfig /all". smdb and nmdb are bound to the wildcard address to accept connections from ppp interfaces created on the fly. Everything seems to work correctly, but my clients cannot use NetBIOS names, when connecting to a share. Connecting to the server by its IP address works with no problem. I am creative, so I decided to disable WINS and use DNS instead. After that, name resolution worked wonderfully. But it's not that easy... by using DNS, my PDC is not able to resolve the netbios names of remote clients, because they don't register their names in DNS when connecting. Is there any way to use WINS on VPN clients? It seems, that Windows silently ignores my WINS server and only tries to resolve names with broadcasting, which is of course not possible through a PPP connection. Do you have any ideas? I use Samba 3.0.28a on my PDC and Windows XP Professional on my client. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba Get an email ID as yourname@ymail.com or yourname@rocketmail.com. Click here http://in.promos.yahoo.com/address
Possibly Parallel Threads
- installing Samba as non-root user at work - please help.
- logon script won't start anymore after update 2.2.3a -> 2.2.8.a
- "Secret is bad" -- Winbind with Samba 2.2.2 and Windows 2000 (native mode)
- samba group rights problem (Domain Admins not working)
- Help with samba implementation