[pptp-server] neibourhood network problem ...

Tue Oct 3 13:09:11 CDT 2000

Netbeui, netbios.. tomato.. tomatoe... The point is that those packets are
non routable so there is no way to poll the master browser if it resides on
the side of the network past the VPN server.

Unless he does what you recommended (which depends on how complicated his
network is...) he isn't going to browse the network neighborhood.

Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
----- Original Message -----
From: "Steve Cody" <SCody at gulbrandsen.com>
To: "PPTP List (E-mail)" <pptp-server at lists.schulte.org>
Sent: Tuesday, October 03, 2000 1:22 PM
Subject: RE: [pptp-server] neibourhood network problem ...

> The Network Neighborhood is a list of the systems that the Master Browser
> knows about.  It does not rely on Netbeui to work, but Netbios.  The
entries
> in the tcp dump were Netbios broadcasts.  If your client computer cannot
> communicate with the Master Browser, or thinks it is the Master Browser,
> then it will not have a list of computers, or may take awhile to build a
> list (if the broadcasts work).
>
> The best way for you to be able to browse the Network Neighborhood would
be
> to use a WINS server.  The other method is to set up lmhosts files on each
> client (or just the remote pptp client(s)).  The Network Neighborhood
> doens't need to be crucial to your network access.  You said that you
could
> access the computers by doing a \\computername at the RUN menu.  One other
> thing, if you try to access a computer that way and receive an error, it
may
> be because it can't resolve the IP address from the Netbios name of the
> computer.  In those cases, you can type \\ipaddressofserver at the RUN
menu
> and access the resources that way.  When viewing the resources of another
> computer using this method, you can map network drives to their resources
to
> make the connections easier in the future, and you can also drag the
shared
> folder to your desktop to create a shortcut to it.
>
> The browsing problem you are having is a Windows issue, not a pptp issue.
> If you need any more help, let me know and I'll send you some Microsoft
> Qxxxxxx articles on it.
>
> I hope this was of some assistance to you.
>
> Steve Cody, MCSE
> Information Systems Administrator
> Gulbrandsen Manufacturing, Inc.
> Office - 803.531.2413 x102
> Email - scody at gulbrandsen.com
>
>
> -----Original Message-----
> From: Adam Lang [mailto:aalang at rutgersinsurance.com]
> Sent: Tuesday, October 03, 2000 12:41 PM
> To: Pptp
> Subject: Re: [pptp-server] neibourhood network problem ...
>
>
> Network neighborhood uses netbuei, correct?  Net beui is non routing, so
it
> can't broadcast into that network to find the other shares.
>
> That would be my theory.
>
> Adam Lang
> Systems Engineer
> Rutgers Casualty Insurance Company
> ----- Original Message -----
> From: "Jean-Paul Chavant" <chavant at geosys.fr>
> To: "Pptp" <pptp-server at lists.schulte.org>
> Sent: Tuesday, October 03, 2000 11:30 AM
> Subject: [pptp-server] neibourhood network problem ...
>
>
> > hello,
> >
> > My VPN connexion works very well. BUT, when i browse the network from my
> > client with the neibourhood network i see only me (the client) (RQ : i
see
> > only one time all the computer in the window. after deconnecting and re
> > connecting i see nothing ...). When i execute \\computer_name, a windows
> is
> > openned and i see shares (but the computer doesn't appears in the
> > neibourhood network window ...).
> >
> > I ve made a tcpdump on the ppp interface of the connection. here is the
> > result :
> >
> > my client is 192.168.0.100
> > my server ppp is 192.168.0.1
> > my wins is 192.168.1.3 and 192.168.3.2
> >
> > tcpdump: listening on ppp0
> > 17:24:41.715057 192.168.0.100.netbios-dgm > 192.168.0.255.netbios-dgm:
udp
> > 177
> > 17:24:41.715107 192.168.0.1 > 192.168.0.100: icmp: net 192.168.0.255
> > unreachable [tos 0xc0]
> > 17:24:41.733422 192.168.0.100.netbios-dgm > 192.168.0.255.netbios-dgm:
udp
> > 177
> > 17:24:41.733466 192.168.0.1 > 192.168.0.100: icmp: net 192.168.0.255
> > unreachable [tos 0xc0]
> > 17:24:42.227152 192.168.0.100.netbios-dgm > 192.168.0.255.netbios-dgm:
udp
> > 177
> > 17:24:42.227198 192.168.0.1 > 192.168.0.100: icmp: net 192.168.0.255
> > unreachable [tos 0xc0]
> > 17:24:42.240954 192.168.0.100.netbios-dgm > 192.168.3.191.netbios-dgm:
udp
> > 177
> > 17:24:42.734865 192.168.0.100.netbios-dgm > 192.168.0.255.netbios-dgm:
udp
> > 177
> > 17:24:42.734926 192.168.0.1 > 192.168.0.100: icmp: net 192.168.0.255
> > unreachable [tos 0xc0]
> > 17:24:42.748635 192.168.0.100.netbios-dgm > 192.168.3.191.netbios-dgm:
udp
> > 177
> > 17:24:43.242621 192.168.0.100.netbios-dgm > 192.168.0.255.netbios-dgm:
udp
> > 177
> > 17:24:43.242680 192.168.0.1 > 192.168.0.100: icmp: net 192.168.0.255
> > unreachable [tos 0xc0]
> > 17:24:43.256246 192.168.0.100.netbios-dgm > 192.168.3.191.netbios-dgm:
udp
> > 177
> > 17:24:43.750179 192.168.0.100.netbios-dgm > 192.168.0.255.netbios-dgm:
udp
> > 177
> > 17:24:43.750238 192.168.0.1 > 192.168.0.100: icmp: net 192.168.0.255
> > unreachable [tos 0xc0]
> > 17:24:43.764065 192.168.0.100.netbios-dgm > 192.168.3.191.netbios-dgm:
udp
> > 177
> > 17:24:44.257925 192.168.0.100.netbios-dgm > 192.168.0.255.netbios-dgm:
udp
> > 200
> > 17:24:44.257982 192.168.0.1 > 192.168.0.100: icmp: net 192.168.0.255
> > unreachable [tos 0xc0]
> > 17:24:44.271527 192.168.0.100.netbios-ns > 192.168.3.2.netbios-ns: udp
50
> > 17:24:44.272127 192.168.3.2.netbios-ns > 192.168.0.100.netbios-ns: udp
62
> > (DF)
> > 17:24:44.286659 192.168.0.100.1063 > 192.168.1.106.netbios-ssn: S
> > 2250926:2250926(0) win 8192 <mss 1422,nop,wscale 0,nop,nop,timestamp 0
> > 0,nop,nop,sackOK> (DF) [tos 0xb4]
> > 17:24:44.287819 192.168.1.106.netbios-ssn > 192.168.0.100.1063: S
> > 34150685:34150685(0) ack 2250927 win 8532 <mss 1460,nop,nop,sackOK> (DF)
> > 17:24:44.298899 192.168.0.100.1063 > 192.168.1.106.netbios-ssn: . ack 1
> win
> > 8532 (DF) [tos 0xb4]
> > 17:24:44.311924 192.168.0.100.1063 > 192.168.1.106.netbios-ssn: P
1:73(72)
> > ack 1 win 8532 (DF) [tos 0xb4]
> > 17:24:44.312348 192.168.1.106.netbios-ssn > 192.168.0.100.1063: P 1:5(4)
> ack
> > 73 win 8460 (DF)
> > 17:24:44.449233 192.168.0.100.1063 > 192.168.1.106.netbios-ssn: . ack 5
> win
> > 8528 (DF) [tos 0xb4]
> > 17:24:45.012402 192.168.0.100.1063 > 192.168.1.106.netbios-ssn: P
> > 73:231(158) ack 5 win 8528 (DF) [tos 0xb4]
> > 17:24:45.013063 192.168.1.106.netbios-ssn > 192.168.0.100.1063: P
5:86(81)
> > ack 231 win 8302 (DF)
> > 17:24:45.027746 192.168.0.100.1063 > 192.168.1.106.netbios-ssn: P
> > 231:384(153) ack 86 win 8447 (DF) [tos 0xb4]
> > 17:24:45.032217 192.168.1.106.netbios-ssn > 192.168.0.100.1063: P
> 86:142(56)
> > ack 384 win 8149 (DF)
> > 17:24:45.040314 192.168.0.100.1063 > 192.168.1.106.netbios-ssn: P
> > 384:483(99) ack 142 win 8391 (DF) [tos 0xb4]
> > 17:24:45.040911 192.168.1.106.netbios-ssn > 192.168.0.100.1063: P
> > 142:252(110) ack 483 win 8050 (DF)
> > 17:24:45.062483 192.168.0.100.1063 > 192.168.1.106.netbios-ssn: P
> > 483:582(99) ack 252 win 8281 (DF) [tos 0xb4]
> > 17:24:45.063076 192.168.1.106.netbios-ssn > 192.168.0.100.1063: P
> > 252:358(106) ack 582 win 7951 (DF)
> > 17:24:45.082843 192.168.0.100.1063 > 192.168.1.106.netbios-ssn: P
> > 582:681(99) ack 358 win 8175 (DF) [tos 0xb4]
> > 17:24:45.083406 192.168.1.106.netbios-ssn > 192.168.0.100.1063: P
> > 358:468(110) ack 681 win 7852 (DF)
> > 17:24:45.204080 192.168.0.100.1063 > 192.168.1.106.netbios-ssn: . ack
468
> > win 8065 (DF) [tos 0xb4]
> > 17:24:47.152517 192.168.0.100.1063 > 192.168.1.106.netbios-ssn: P
> > 681:720(39) ack 468 win 8065 (DF) [tos 0xb4]
> > 17:24:47.152980 192.168.1.106.netbios-ssn > 192.168.0.100.1063: P
> > 468:507(39) ack 720 win 7813 (DF)
> > 17:24:47.166714 192.168.0.100.1063 > 192.168.1.106.netbios-ssn: F
> 720:720(0)
> > ack 507 win 8026 (DF) [tos 0xb4]
> > 17:24:47.167059 192.168.1.106.netbios-ssn > 192.168.0.100.1063: F
> 507:507(0)
> > ack 721 win 7813 (DF)
> > 17:24:47.180298 192.168.0.100.1063 > 192.168.1.106.netbios-ssn: . ack
508
> > win 8026 (DF) [tos 0xb4]
> >
> > 46 packets received by filter
> > 0 packets dropped by kernel
> >
> >
> > first : why my client ask for 192.168.3.191 ? this computer & IP doesn't
> > exist !!!
> >
> > in the tcpdump whet does means the last number ?
> > 17:24:43.764065 192.168.0.100.netbios-dgm > 192.168.3.191.netbios-dgm:
udp
> > 177
> >
> > ^^^
> >
> > Why i have this error : 17:24:44.257982 192.168.0.1 > 192.168.0.100:
icmp:
> > net 192.168.0.255 unreachable [tos 0xc0] ?
> >
> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >
> > JPaul
> >
> > _______________________________________________
> > pptp-server maillist  -  pptp-server at lists.schulte.org
> > http://lists.schulte.org/mailman/listinfo/pptp-server
> > List services provided by www.schulteconsulting.com!
>
> _______________________________________________
> pptp-server maillist  -  pptp-server at lists.schulte.org
> http://lists.schulte.org/mailman/listinfo/pptp-server
> List services provided by www.schulteconsulting.com!
> _______________________________________________
> pptp-server maillist  -  pptp-server at lists.schulte.org
> http://lists.schulte.org/mailman/listinfo/pptp-server
> List services provided by www.schulteconsulting.com!