[pptp-server] Almost there...!

[Robinson, Eric]

WINS does not provide the browse list. It provides NetBIOS name resolution
only, which the client can use to locate a master browser on its subnet. The
browse list is provided by the elected master browser or an appointed backup
browser, which are machines (not necessarily servers) that have the computer
browser service turned on. Often the WINS server is also a master browser,
but not necessarily since the two functions are completely separate. You may
not need Network Neighborhood style browsing, but you will certainly save
yourself a lot of time by enabling WINS. Otherwise, you do have to create an
LMHOSTS file on every machine to perform local name resolution.

--Eric

-----Original Message-----
From: John Van Ostrand [mailto:john at netdirect.ca]
Sent: Tuesday, May 23, 2000 5:06 AM
To: 'MarkT at govirtual.com.au'; pptp-server at lists.schulte.org
Subject: RE: [pptp-server] Almost there...!


Mark,

You need a WINS server. The WINS server provides the "browse list" (see in
Network Neighborhood) and provides the translation from name to IP address
(needed when opening a system from Network Neighborhood.) Without these you
will not be able to browse the remote Win98 systems, you can, however,
access these systems without WINS using an LMHOSTS file.

To setup a WINS server use Samba and configure /etc/smb.conf The lines you
care about are:

	workgroup = WORKGROUP
	wins support = yes

Then setup TCP/IP on your LAN based workstations to use your Linux system as
the WINS server. You can set the remote systems automatically if you have
the ms-wins option in your /etc/ppp/options file.

If you don't need browsing and just want to access the systems you can use
the LMHOSTS feature of Windows. Edit the \Windows\LMHOSTS file and create an
entry for each system you want to access. If memory serves the line would
look like this for an IP address of 1.2.3.4 and a system name of ACCT

	1.2.3.4		ACCT

One final note: You should consider using Samba as a file/print server for
your LAN. Samba can act like a Windows NT domain controller authenticating
your users when they boot their systems. Just add the line:

	security = user
	encrypt passwords = yes
	domain logons = yes

Then create a netlogon share. Create users using the smbpasswd program.

To setup the client, add Client for Microsoft Networks in the Network
Control panel, set it to be the default login, and set its properties to
logon to the domain you specified in smb.conf (workgroup = ). I also set the
workgroup in the network control panels identification tab.

John.

> -----Original Message-----
> From: Mark Turner [mailto:MarkT at govirtual.com.au]
> Sent: Monday, May 22, 2000 9:43 PM
> To: pptp-server at lists.schulte.org
> Subject: [pptp-server] Almost there...!
> 
> 
> I've installed, configured & tested my first PPTP tunnel.
> Pinged other machines on the LAN fine!
> Real happy about this.
> 
> I'm expecting to be able to 'see' other machines via the 
> (Win98) Network
> Browser on the remote client. Not yet.
> 
> The fact that the Ping's are OK indicates the tunnel is fine. (Yup?).
> 
> What else do I have to do to have Win packets visible? I'm not running
> any servers on the LAN. Just peer to peer Win networking.
> 
> Any comments greatly appreciated.
> 
> Packet of Tim Tams if you're in Sydney.
> 
> Regards, Mark Turner
> 
> _______________________________________________
> pptp-server maillist  -  pptp-server at lists.schulte.org
> http://lists.schulte.org/mailman/listinfo/pptp-server
> List services provided by www.schulte.org!
> 
_______________________________________________
pptp-server maillist  -  pptp-server at lists.schulte.org
http://lists.schulte.org/mailman/listinfo/pptp-server
List services provided by www.schulte.org!