logging in to the domain through a VPN

[Rik]

I'm going crazy trying to make it easy for my remote
users to get their email and access to the LAN from
outside of the office.

I have TWO (yes, 2) vpn tests going on. One Symantec
Veloceraptor 1100 and one Cisco 2621 router w/the vpn
option.

In both tests, I am having trouble getting users who
start their laptops logging in to "workstation only", and
then later connect to the internet via AOL to
authenticate to the email server and/or the domain. This
problem is happening on Win2k and Win98 laptops. (my CEO
likes his VAIO C1-X and i can't get him to upgrade to XP)


I tried (with the cisco client) to run a batch file with
the following command:

net use \\emailserver\f /user:TARATOY\jsmith
password /PERSISTENT:YES

(F, bring a CDROM)

This sometimes works - but is not perminent. Users loose
connection to the domain and get various messages either
asking to re-logon or that the credentials conflict.
Sometimes, it doesn't work at all.

Is there a utility in the resource kits or a better
command to try in the batch file?

The laptops are set up on the domain and made to register
on the domain (its not AD - we still have an NT domain
structure at least until next year) We also have Novell
5.1 - getting a connection to the NetWare servers (there
are 2 of them) would be a great bonus!

Any thoughts, anyone?

Thanks in advance.
-Rik

 

[hal]

I'm going crazy trying to make it easy for my remote
users to get their email and access to the LAN from
outside of the office.

I have TWO (yes, 2) vpn tests going on. One Symantec
Veloceraptor 1100 and one Cisco 2621 router w/the vpn
option.

In both tests, I am having trouble getting users who
start their laptops logging in to "workstation only", and
then later connect to the internet via AOL to
authenticate to the email server and/or the domain. This
problem is happening on Win2k and Win98 laptops. (my CEO
likes his VAIO C1-X and i can't get him to upgrade to XP)

It may be an AOL issue. Try a test from another ISP that will give
you a legal IP. NAT (PAT/NAPT) does wierd things to IPSEC. I tried
and tried for weeks to get a Checkpoint SecureClient VPN working with
our firewall using a local ISP that did private address NATing (PAT)
with no luck. Switched over to another ISP with legals, and
everything worked great. I think AOL NATs.

Hal

 

[Keith Langmead]

Yeah, as far as I'm aware AOL does some weird things with the connection,
beyond just NATing, which makes it extremely un-VPN friendly. I think the
problem is something to do with AOL not allowing some sorts of
authentication information to be transmitted through its network, which can
also cause problems if you have a secure public web server using NT
Integrated authentication.

Try another ISP and it'll hopefully work.

Keith