VPN Connection suddenly very slow

[Jim]

I have a W2K SP3 server running as a VPN server. The connection has been up
for about a year without any problems. I also have two terminal servers
running behind the VPN server.

About a week ago, I started having problems with users not being able to get
connected to the terminal servers. I started to key into the terminal
servers because they said they were connecting to the VPN, but not the TS.

I am know thinking that the timeouts to get to the login screen for the TS
is not related to the TS, but instead is the VPN server. A crosscheck for
this is a user that only uses VPN for file access also stated that the
process that used to "fly" now crawls.

I have reviewed the logs on the VPN server, but nothing really stands out.
Users are logging errors stating timeouts, and or bad passwords, but I know
they are putting in the right passwords so I don't think that is it.

I have noted an error about the group policy is not able to be applied
because it could not connect to domain.com.

This morning, I was at a user site and while only connected to VPN, I tried
to ping my servers and it continually timed out. Then after a disconnect
and reconnect, it was fine and the pings were fine, but the TS session was
still timing out.

Any help is greatly appreciated.

Jim

 

[Gene Wilson]

Possible problem with the ISP or the line. Gene

 

[Reggie]

Does your internal domain use a *.com or *.net to resolve
internal host?

 

[Jim]

It is not the ISP

Possible problem with the ISP or the line. Gene

 

[Jim]

I am not sure how to tell but am assuming it is .com.

An additional note to call out is that the server event log states that it
cannot find the browser. I have looked for errors using google and it says
its a multi-homed server and both nics must have the same subnet mask. I
thought that VPN was suppose to have different subnet masks because routing
and remote did the job of routing?

Jim

 

[Bill Grant]

If the RRAS server is also a DC, the name resolution (both DNS and
Netbios/WINS) can be affected when the server acquires an additional
("virtual") IP. This can also affect the browser service, because the browse
master is now multihomed. (The server will normally be the master browser,
and must be the domain master browser if it is the first or only server in
the network).

See MS KB 292822 for more info on this. For browser problems,
particularly note the bit about disabling Netbios over TCP/IP on the
"virtual" interface.