quoted from
http://www.ChicagoTech.net
Unable to browse through PPTP/VPN connection
Symptoms: 1. If the WINS server is on the same computer as the PPTP/VPN
server, and you attempt to connect to a computer using a PPTP/VPN client,
you may experience following problem: 1) The NetBIOS name of the computer to
which you are attempting to connect is not resolved. 2) You may receive an
error message similar to the following error message: "System error 53 has
occurred. The network path was not found" when using net view or opening
Network Knighthood.
2. If the WINS server is not on the same computer as the PPTP server and you
attempt to connect to a computer using a PPTP client, you may be able to
connect to computers on your local area network (LAN), but you may be unable
to connect to network shares or resources on the PPTP server.
Resolutions: Inability to browse often means the client can't resolve
NetBIOS names.
1. If this is a workgroup network, enable NetBIOS over TCP/IP on the server
and clients.
2. If this is domain network and the WINS server is on the same computer as
the PPTP/VPN server, move the WINS server to a different computer.
3. Add the NetBEUI protocol for your PPTP tunnel instead of, or in addition
to, TCP/IP.
4. By default, most routers and firewalls prevent the transmission of
NetBIOS names unless you enable UDP ports 137 and 138 and TCP port 139. Try
to enable UDP ports 137 and 138 and TCP port 139 across all routers and
firewalls between the PPTP/VPN client and PPTP/VPN server.
5. Make sure the client has correct DNS, WINS and Master Browser settings.
6. Make sure the default gateway points to the remote network rather than to
the ISP.
7. Some ISP might block ports required for NetBIOS name broadcasts.
8. If WINS address is not distributed upon connection to VPN, LMHOSTS should
be configured to enable Domain to be located.
9. If you try these techniques and the client still can't browse, try to use
UNC to connect to the remote resources by ip, for example, use the net use
h: \\serverip\sharename command.
--
For more and other information, go to
http://www.ChicagoTech.net
Don't send e-mail or reply to me except you need consulting services.
Posting on MS newsgroup will benefit all readers and you may get more help.
Robert Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN, Anti-Virus, Tips & Troubleshooting on
http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.
"Covarde Anonimo" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) m...
> hi ppl,
>
>
> i'm cross-posting this to both linux and windows groups because i
> don't know in which side the solution is.
>
> i just finished configuring two linux firewalls in two separate
> networks. each network has it's own win2000 PDC with it's own domain,
> and between the two are 2 linux firewall's, one of them is a pptp
> server (internal network is 192.168.2.0/24) and the other is a pptp
> client (internal network is 192.168.1.0/24). routing is configured
> correctly and from any given 192.168.2.x machine i can ping and access
> shares in any random 192.168.1.x machine.
>
> problem is, i did this job as a contractor, i don't have autonomy to
> replace pptp by ipsec neither to replace the win2000 PDCs by Samba.
> and my client want's to browse BOTH networks from any machine in any
> network. he want's to be able to see all machines in the 192.168.2.0
> network from a 192.168.1.x and the other way around.
>
> is this possible to do ? how do i do this ?
>
> enabling netBIOS broadcasts over the tunnel or enabling some stuff on
> the PDCs ?
>
> if the answer is on the PDCs, remember that i'm more a linux type than
> windows. what concerns to windows i need to baby-step instructions
> because is unknown territory for me.
>
> thanks,
>
> Bento Loewenstein
>
> PS.: if possible CC the answers to my e-mail. tks.
Similar Threads
Linear Mode
