M
Mark R.
I have a native mode W2K AD environment. On the perimeter
is a PIX 515 (sorry, not ISA Server, yet) as is my
perimeter defense. the PIX also does P-NAT for our office.
On the inside LAN I have a W2K member server that only
exists to provide incoming VPN authentication and DHCP to
requestors. On the PIX is a static route and access list
that moves all PPTP/GRE traffic into the network to the
VPN server for authentication. However, here is the issue.
Only some users are allowed authentication, and then they
only remain connected for about a minute and a half. The
ones that never connect get all the way to "verifying
username and password", it sits there for about 30
seconds, then the "error 721" box pops up telling you that
the "remote computer did not respond...yadda, yadda". The
event logged on the VPN server for the clients that
successfully connect and are dropped shortly thereafter is
a happy message about being logged off because of user
request (sorry, don't have the exact event id). We've
tried both W2K and XP clients, with encryption on and off
with the same results. Also, the users that can connect
can do it from pretty much any machine, while the ones
that cannot connect are in the same boat (cannot connect
from anywhere). We're not doing any fancy-schmancy
VLANning or weird layer 3 switching (I hope...will have to
check further up the food chain on that one).
Anyhow...sorry to ramble. Lemme know if there are ideas
out there.
Mark
is a PIX 515 (sorry, not ISA Server, yet) as is my
perimeter defense. the PIX also does P-NAT for our office.
On the inside LAN I have a W2K member server that only
exists to provide incoming VPN authentication and DHCP to
requestors. On the PIX is a static route and access list
that moves all PPTP/GRE traffic into the network to the
VPN server for authentication. However, here is the issue.
Only some users are allowed authentication, and then they
only remain connected for about a minute and a half. The
ones that never connect get all the way to "verifying
username and password", it sits there for about 30
seconds, then the "error 721" box pops up telling you that
the "remote computer did not respond...yadda, yadda". The
event logged on the VPN server for the clients that
successfully connect and are dropped shortly thereafter is
a happy message about being logged off because of user
request (sorry, don't have the exact event id). We've
tried both W2K and XP clients, with encryption on and off
with the same results. Also, the users that can connect
can do it from pretty much any machine, while the ones
that cannot connect are in the same boat (cannot connect
from anywhere). We're not doing any fancy-schmancy
VLANning or weird layer 3 switching (I hope...will have to
check further up the food chain on that one).
Anyhow...sorry to ramble. Lemme know if there are ideas
out there.
Mark