[pptp-server] Net Neighborhood is misbehavin'
Robert Dege
rcd at amherst.com
Mon Feb 26 11:12:31 CST 2001
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.
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.
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).
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".
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.
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
+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
More information about the pptp-server
mailing list