[pptp-server] Net Neighborhood is misbehavin'

[Robert Dege]

I apologize for my silence, but I quickly discovered what happens to 
your linux box when you upgrade to PC133 RAM & your machine goes *yuck*

Anways, upon some investigation, I discovered that most of the NT 
machines here on my Network have a Protocol installed by Novell called 
'NWLink NetBIOS'.  So in short, almost 60% of the company is using 
IPX/SPX to communicate NetBIOS.  So I switched the binding order on 1 NT 
machine, so that NetBIOS was bound to the NIC card instead of the IPX 
protocol, and I could find it under `Find Computer` on the PPTP Client.

Thanks for the help on that one.  I still need to figure out the 
Workgroups problem (or if it's inter-related with the above problem).  
I'll let you know of my findings.

-Rob

>> -----Original Message-----
>> From: robert [mailto:berzerke at swbell.net]
>> Sent: Monday, February 26, 2001 10:02 PM
>> To: Robert Dege
>> Cc: pptp-server
>> Subject: Re: [pptp-server] Net Neighborhood is misbehavin'
>> 
>> Yes, and that is the problem. From the 2.4 Kernel PPTPD Howto:
>> 
>> 5.10    Q: Browsing doesn't work.  How do I fix it?
>> <snip>
>>  
>> A: Are *ANY* of the clients running more than one  protocol?
>> From the Samba docs: "Every NetBIOS machine take part in a
>> process of electing the LMB [Local Master Browser] (and DMB
>> [Domain Master Browser]) every 15 minutes...The election
>> process is "fought out" so to speak over every NetBIOS 
>> network interface. In the case of a Windows 9x machine that 
>> has both TCP/IP  and IPX installed and has NetBIOS enabled
>> over both protocols the election will be decided over both
>> protocols. As often happens, if the Windows 9x machine is
>> the only one with both protocols then the LMB may be won on
>> the NetBIOS interface over the IPX protocol. Samba will then
>> lose the LMB role as Windows 9x will insist it knows who the
>> LMB is. Samba will then cease to function as an LMB and thus
>> browse list operation on all TCP/IP only machines will fail.
>> 
> 
> I could be way off base here (its been a few years) but I seem to remember
> having a similar problem as described above. To make a long story short, I
> thought we fixed the problem by changing the binding order of the protocols
> to give TCP/IP precedence. 
> 
> I just checked the MS site and couldn't find the article I remember reading,
> but I seem to remember either editing a registry setting or (on NT) goto
> network->properties->bindings and "move-up/move-down" the protocol binding
> order.
> 
> Just a thought!
> 
> Steve Cowles
> _______________________________________________
> pptp-server maillist  -  pptp-server at lists.schulte.org
> http://lists.schulte.org/mailman/listinfo/pptp-server
> List services provided by www.schulteconsulting.com!
> 
> 
>