VPN network browsing

Hi, folks.

Trying to set up a VPN for our office to use as part of remote access for
home users. We've got a file/application server, an Exchange server, and a
VPN server all behind a SonicWall firewall. I've set up the VPN server for
routing and remote access, I've given it a pool of static IDs to work from,
I've told the firewall to permit traffic to the appropriate ports, that's all
fine. Users can connect to the VPN server using the New Connection Wizard to
open their connection the first time and their saved desktop connections next
time. No fancy clients, just MS's built in VPN client.

Unfortunately, once they're in- logged in and everything using their user
name and domain name- they can't browse the network. I've tried using
standard machine names and fully qualified machine names alike. No good. I've
got the client computer's workgroup set to the name of the office domain. No
good. The DNS for the VPN connection is set to the domain controller's DNS,
and the domain controller's domain suffix is being used as the client's
domain suffix. On the server end, enable broadcast name resolution is in
place, and NetBIOS over TCPIP is enabled on both ends.

I haven't installed WINS yet and I don't think I want to if DNS is in place,
unless there's something going on that I've missed. Most of the time VPN
users can ping other servers on the network, although they'll get the
occasional dropped packet. Anyone have any suggestions what to do? All the
servers are running Windows Server 2003, and the home machines are running XP
Professional Edition with Service Pack 2. No Windows firewall, although one
of the machines has Zone Alarm free edition installed and running.

1. it could be the cached credtentials issue. what do you receive if using net view command?
2. this may answer dropping vpn connection. quoted http://howtonetworking.com.

"The Network name is no longer available"

VPN drops the connection.

VPN is very slow.



Symptom: 1. You have setup VPN to connect two offices through DLS line successfully. The both offices can browse over the VPN without problem. You can copy a small file between two offices but it may drop the VPN connection when copying a large file and receive this message: "The Network name is no longer available".

2. You have setup a VPN server in the office for home users accessing through DSL line. The VPN clients can access the office without any problems. However, the speed is very slow. Also, you may receive "The Network name is no longer available" message when Iyou try to copy a file from the VPN client to the Server.



Resolution: modify the MUT.



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.

Bob Lin, MS-MVP, MCSE & CNE
How to Setup Windows, Network, Remote Access on http://www.HowToNetworking.com
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.
I recommend Brinkster for web hosting!

"Camwyn" <(E-Mail Removed)> wrote in message news:72FA9AE8-C9FD-449D-B47E-(E-Mail Removed)...
Hi, folks.

Trying to set up a VPN for our office to use as part of remote access for
home users. We've got a file/application server, an Exchange server, and a
VPN server all behind a SonicWall firewall. I've set up the VPN server for
routing and remote access, I've given it a pool of static IDs to work from,
I've told the firewall to permit traffic to the appropriate ports, that's all
fine. Users can connect to the VPN server using the New Connection Wizard to
open their connection the first time and their saved desktop connections next
time. No fancy clients, just MS's built in VPN client.

Unfortunately, once they're in- logged in and everything using their user
name and domain name- they can't browse the network. I've tried using
standard machine names and fully qualified machine names alike. No good. I've
got the client computer's workgroup set to the name of the office domain. No
good. The DNS for the VPN connection is set to the domain controller's DNS,
and the domain controller's domain suffix is being used as the client's
domain suffix. On the server end, enable broadcast name resolution is in
place, and NetBIOS over TCPIP is enabled on both ends.

I haven't installed WINS yet and I don't think I want to if DNS is in place,
unless there's something going on that I've missed. Most of the time VPN
users can ping other servers on the network, although they'll get the
occasional dropped packet. Anyone have any suggestions what to do? All the
servers are running Windows Server 2003, and the home machines are running XP
Professional Edition with Service Pack 2. No Windows firewall, although one
of the machines has Zone Alarm free edition installed and running.

1. When I attempted net view //192.168.0.180 (the domain controller, which is
also our main file server), it made the attempt for some time, then said
'network error 53'.

2. MUT?

"Robert L [MS-MVP]" wrote:

> 1. it could be the cached credtentials issue. what do you receive if using net view command?
> 2. this may answer dropping vpn connection. quoted http://howtonetworking.com.
>
> "The Network name is no longer available"
>
> VPN drops the connection.
>
> VPN is very slow.
>
>
>
> Symptom: 1. You have setup VPN to connect two offices through DLS line successfully. The both offices can browse over the VPN without problem. You can copy a small file between two offices but it may drop the VPN connection when copying a large file and receive this message: "The Network name is no longer available".
>
> 2. You have setup a VPN server in the office for home users accessing through DSL line. The VPN clients can access the office without any problems. However, the speed is very slow. Also, you may receive "The Network name is no longer available" message when Iyou try to copy a file from the VPN client to the Server.
>
>
>
> Resolution: modify the MUT.
>
>
>
> 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.
>
> Bob Lin, MS-MVP, MCSE & CNE
> How to Setup Windows, Network, Remote Access on http://www.HowToNetworking.com
> Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
> This posting is provided "AS IS" with no warranties.
> I recommend Brinkster for web hosting!
>
> "Camwyn" <(E-Mail Removed)> wrote in message news:72FA9AE8-C9FD-449D-B47E-(E-Mail Removed)...
> Hi, folks.
>
> Trying to set up a VPN for our office to use as part of remote access for
> home users. We've got a file/application server, an Exchange server, and a
> VPN server all behind a SonicWall firewall. I've set up the VPN server for
> routing and remote access, I've given it a pool of static IDs to work from,
> I've told the firewall to permit traffic to the appropriate ports, that's all
> fine. Users can connect to the VPN server using the New Connection Wizard to
> open their connection the first time and their saved desktop connections next
> time. No fancy clients, just MS's built in VPN client.
>
> Unfortunately, once they're in- logged in and everything using their user
> name and domain name- they can't browse the network. I've tried using
> standard machine names and fully qualified machine names alike. No good. I've
> got the client computer's workgroup set to the name of the office domain. No
> good. The DNS for the VPN connection is set to the domain controller's DNS,
> and the domain controller's domain suffix is being used as the client's
> domain suffix. On the server end, enable broadcast name resolution is in
> place, and NetBIOS over TCPIP is enabled on both ends.
>
> I haven't installed WINS yet and I don't think I want to if DNS is in place,
> unless there's something going on that I've missed. Most of the time VPN
> users can ping other servers on the network, although they'll get the
> occasional dropped packet. Anyone have any suggestions what to do? All the
> servers are running Windows Server 2003, and the home machines are running XP
> Professional Edition with Service Pack 2. No Windows firewall, although one
> of the machines has Zone Alarm free edition installed and running

He probably wanted to talk about MTU


> 2. MUT?
>