Cannot browse network share files 1

[kiltydave]

I have a VPN connected succesfully between a Win2k server acting as the client and a Linux Server running mitel networks SME server, the VPN connects fine andaccepts my authorisation, but when I try to browse for the shared files via network neighbour hood it does not show any other computers on the network.
The Win2k Server does have its own domain, the linux server is not part of it

any solutions or possible pointers in the right direction are greatly appreciated

 

[MattWray]

You may need to add hosts manually to make this work. I have read about nothing but trouble trying to browse thru Net Places over VPN...

Thanks,

Matt Wray

GFH

http://www.sss-steel.com

 

[ChicagoTechNet]

Matt has a good point. I would like to add more resolutions. 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.


Robert Lin, MS-MVP, MCSE & CNE
Windows, Network, Internet, VPN, Routing and How to at

http://www.ms-mvps.com

 

[kiltydave]

I have tried two things from the last two replies I got one was to add the Ip and domain name into the hosts file, I also setup netbios over TCP/IP the net bios caused me a error 733 and the addition to the hosts file seemed to have no effect

 

[kiltydave]

Me again

It has been recommended that I might need to install samba on the server and client machines is this correct?

 

[MattWray]

If you want to access the shares on the Linux box, you will probably have to set up SAMBA. You might want to try this in the Linux forum, forum54. Real sharp group of people there...

Thanks,

Matt Wray

GFH

http://www.sss-steel.com