Hi, list! I hope the thing I am after is easily done or at least well documented. Somehow I did not find any hint this far. So I have a Linux box here, running Samba 2.0.7, a LAN with Windows 98 machines, and a modem on the server. Some users want to dial the server from their Windows laptops when they are away, and access the samba shares of the server and the clients on the LAN. I read through the documentation, and have managed to set things up so that the client sees the server. But To achieve this, in smb.conf I had to add an interfaces line, listing the IP address of the ppp link. But now, I cannot start nmbd if the link is not up, because it complains about not being able to bind to the IP. Using ppp0 instead of the IP address was even worse, it simply did not work. I might change the two smb.conf files when some user dials in, and restart the daemons, but this is not pretty, and I fear it destroys active connections like file copy from the server, etc. In smb.conf man page I found PPP mentioned in the section bind interfaces only: Note that you should not use this parameter for machines that are serving PPP or other intermittent or non-broadcast network interfaces as it will not cope with non- permanent interfaces. That's all the lead I have this far. The other problem which is a much smaller one, is that I set the dialin server up, so that it gives a fix IP address to the dialler. I gave the IP address a name in DNS, but if the laptop thinks its netbios name is something different, I cannot access it from the server. It works from the laptop though, and that is the important part. Regards Gee(@freemail.hu)
Gabor, On Mon, 23 Oct 2000 22:25:46 +0200, Nagy Gabor Peter wrote:>To achieve this, in smb.conf I had to add an interfaces line, listing >the IP address of the ppp link. But now, I cannot start nmbd if the >link is not up, because it complains about not being able to bind to >the IP.You might try something like this: Rename your smb.conf to smb.conf.global, delete "interfaces = xxx". Create a new smb.conf like this: [global] interfaces = xxx include = /path/to/your/smb.conf.global Now start nmbd with "-s /path/to/your/smb.conf.global". This will prevent nmbd from seeing your interfaces configuration. Regards, Robert -- --------------------------------------------------------------- Robert.Dahlem@gmx.net Fax +49-69-432647 --------------------------------------------------------------- Sent using PMMail (http://www.pmmail2000.com) - fast, decent, email software; far better than Outlook. Try it sometime.
Nagy Gabor Peter wrote:> > Hi, list! > > I hope the thing I am after is easily done or at least well documented. > Somehow I did not find any hint this far. > > So I have a Linux box here, running Samba 2.0.7, a LAN with Windows 98 > machines, and a modem on the server. > > Some users want to dial the server from their Windows laptops when they > are away, and access the samba shares of the server and the clients on > the LAN. > > I read through the documentation, and have managed to set things up > so that the client sees the server. > > But > > To achieve this, in smb.conf I had to add an interfaces line, listing the > IP address of the ppp link. But now, I cannot start nmbd if the link is > not up, because it complains about not being able to bind to the IP. > Using ppp0 instead of the IP address was even worse, it simply did not > work.I don't understand why you used the interfaces line at all. I don't have to, to do this very thing, and the man page says that by default samba uses all interfaces the kernel knows about. Do you have some reason to limit interfaces?> > > The other problem which is a much smaller one, is that I set the dialin > server up, so that it gives a fix IP address to the dialler. I gave the > IP address a name in DNS, but if the laptop thinks its netbios name is > something different, I cannot access it from the server. It works from > the laptop though, and that is the important part. >I'm not sure I follow you here, but I had a problem where a machine that was usually Ethernetted, and thus was known to DNS by a certain IP address, was dialing in; smbclient wanted to talk to it via its usual IP address. I changed 'name resolve order' to put 'hosts' (that's the normal DNS-based resolution) last: name resolve order = lmhosts wins bcast hosts It most likely ends up getting the address from the WINS server. If you do that, there's probably no good reason to even set up the dialin IP address in your DNS configuration. Sorry if that's not your problem or isn't applicable.