[pptp-server] Net Neighborhood is misbehavin'

Mon Feb 26 17:58:44 CST 2001

In the history section, item 3 and 5 contradict each other.  I'll *assume* 
that is a typo in item 3.

One thing that immediately springs to mind is are *ANY* of the clients (or 
servers) running more than one protocol?  If so, this can really screw up the 
elections.  Screwed up elections mean screwed up browsing.

The other thing I noticed is from your comments, it looks like you might be 
running multiple subnets.  Correct?

On Monday 26 February 2001 11:12, Robert Dege wrote:
> Okay, after rigorous testing, I believe that I am ready to post my
> question to the listserv with as much detail that I can provide.
> This is a slightly long read, so go grab yerself a cup of coffee.
>
> Problem: PPTP Client can't browse Network Neighborhood
>
> Some History on Network
> =======================
> 1 - Using a Class B Network (172.28.x.x)
> 2 - Network consists of Win95/98/NT 4.0, Linux, Alphas, etc.
Nice mix.  Must be fun supporting all of them :)
> 3 - No WINS, No DC, everything is Peer-to-Peer
> 4 - Novell issues DHCP to standard clients, and have NDS File server
> 5 - I have the PPTP Server setup as a WINS server (smb.conf pasted below).
> 6 - PPTP client is Win98 & Linux on a laptop.
>
> What works
> ==========
> 1 - PPTP Works.  I can ping, telnet, http://, FTP ANY machine.
Browsing is often a separate issue from connectivity.  This says it is not a 
connectivity problem.

> 2 - When I double-click on Entire Network, I am able to see all the
> workgroups within the network.
> 3 - If I logon to Novell Client, I can successfully access any aspect of
> the Novell tree in Network Neighborhood (no problems detected thus far).
Wins is a MS "invention".  Everything I've seen says that client for 
microsoft networks must be used.  Can't speak with authority on that though.
> 4 - If I do Find Computer, I am able to find a "few" computers.
>
>
> What doesn't work
> =================
> 1 - When I double click on ANY workgroup in "Entire Network", I get
> \\Workgroup inaccessible.
> 2 - Almost 80% of the computers I try to find with "Find Computer" are
> not found.
>
>
> What I've noticed
> =================
> 1 - I can't find any NT machines.
> 2 - I can access the 1 Win2000 computer.
> 3 - I have 6 machines pointed at the WINS server (1 NT, 1 95, 4 Linux).
>   NT still can't be seen by the Client.  95 & Linux machines can be seen
> through "Find Computer".
Wins tends to work best with ALL machines configured to use Wins.

> 4 - I have 1 Linux machine in it's own workgroup (points to WINS).  I
> have the other 3 machines in their own Workgroup (also point to WINS).
> Both Workgroups are also inaccessible through "Entire Network".
> 5 - Since machines are DHCP, it's very difficult to net view from
> Windows to a IP address.  I can only net view the WINS Name.
You might try temporarily assigning a few IP addresses.  However, if they 
don't register with Wins, and broadcasts don't pass, you still won't see 
them. (I don't understand why, I've seen it happen personally.)

>
>
>
> Here are my Config files:
>
> /etc/pptp.conf
> ==============
> debug
> option /etc/ppp/options.pptp
> localip 172.28.254.46
> #I comment this out since I assign IP's statically via PPTP
> #remoteip 172.28.41.40-49
>
>
> /etc/ppp/options
> ================
> lock
>
>
> /etc/ppp/options.pptp
> =====================
> debug
> lock
> name pptp
> ms-dns 172.28.254.1
> ms-wins 172.28.254.46
> 172.28.254.46:
> auth
Some people have better luck with noauth, but this probably isn't the source 
of your problem.

>
> +chap
> +chapms
> +chapms-v2
> chapms-strip-domain
> require-chap
>
> mppe-128
> mppe-40
> mppe-stateless
> require-mppe
> require-mppe-stateless
>
> #Stuff I want to experiment with once PPTP is completely done.
> #lcp-echo-failure 10
> #lcp-echo-timeout 1
> #mru 1450
> #mtu 1450
> #lcp-restart 15
>
> proxyarp
>
>
> /etc/chap-secrets
> =============
> # Secrets for authentication using CHAP
> # client        server  secret                  IP addresses
> #Use IP within same subnet to debug Nethood problem.
> #rcd             pptp    "Rob"                172.28.41.46
> rcd             pptp    "Rob"                172.28.254.10
>
>
> /etc/smb.conf
> =============
> [global]
>          workgroup = PPTP
>          netbios name = Warf
>          server string = PPTP Server
>          log file = /var/log/samba/samba-log.%m
>          max log size = 100
>          security = SHARE
>          encrypt passwords = yes
>          socket options = TCP_NODELAY IPTOS_LOWDELAY
>
>          #Makes Samba the WINS Server
>          wins support = yes
>          name resolve order = wins bcast
>          browse list = yes
>
>          #To Make Samba the Default Master Server upon Election
>          #Good For When I have to restart the Samba Server
>          local master=yes
>          os level=65
>          preferred master=yes
>
> [homes]
>         browseable = no
>         map archive = yes
>
> [test]
>          comment = For testing only, please
>          path = /home/samba
>          read only = no
>          guest ok = yes
>
>
>
> /sbin/ifconfig
> ==============
> eth0      Link encap:Ethernet  HWaddr 00:A0:CC:D7:0E:F7
>            inet addr:172.28.254.46  Bcast:172.28.255.255  Mask:255.255.0.0
>            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>            RX packets:1276688 errors:0 dropped:0 overruns:0 frame:0
>            TX packets:4655 errors:2 dropped:0 overruns:0 carrier:2
>            collisions:0 txqueuelen:100
>            Interrupt:5 Base address:0xd800
>
> eth1      Link encap:Ethernet  HWaddr 00:A0:CC:D6:86:EA
>            inet addr:128.205.228.57  Bcast:128.205.228.63
> Mask:255.255.255.240
>            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>            RX packets:13267 errors:0 dropped:0 overruns:0 frame:0
>            TX packets:1857 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 txqueuelen:100
>            Interrupt:10 Base address:0xd400
>
> lo        Link encap:Local Loopback
>            inet addr:127.0.0.1  Mask:255.0.0.0
>            UP LOOPBACK RUNNING  MTU:3924  Metric:1
>            RX packets:58 errors:0 dropped:0 overruns:0 frame:0
>            TX packets:58 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 txqueuelen:0
>
> ppp0      Link encap:Point-to-Point Protocol
>            inet addr:172.28.254.46  P-t-P:172.28.254.10
> Mask:255.255.255.255
>            UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
>            RX packets:18 errors:0 dropped:0 overruns:0 frame:0
>            TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 txqueuelen:10
>
>
>
> /sbin/ipchains -nL
> ==================
> Chain input (policy ACCEPT):
> Chain forward (policy ACCEPT):
> Chain output (policy ACCEPT):
> #I have no Rules, enabled ipchains for debugging.
>
>
> Finally, My Windows Logon Sequence
> ==================================
> 1. Client for Microsoft network Logon Screen
> 		User -> rcd
> 		 Passwd -> Rob
> 2. Load DUN.
> 3. Enter in User -> rcd, passwd -> Rob
> 4. Successful connection.
>
>
> If there is anything that I can answer, or if anyone can point out
> something that I am missing, please let me know.... no matter how
> insignificant it may seem.
>
>
> Thanks
>
> -Rob
<snip>