Re: VPN Client Connection Issue

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance




Sometimes the problem is just someon else's :-)


--
Phillip Windell

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------


"Jim in Arizona" <tiltowait@xxxxxxxxxxx> wrote in message
news:Oi%23vyBo%23JHA.4560@xxxxxxxxxxxxxxxxxxxxxxx
Good memory Phillip but, at the moment, the ISA server is still under test
conditions and not affecting normal traffic. Our company has a good 16
public IPs for use and current LAN traffic routes out a seperate router (a
linksys router of all things) to the net. I'm still testing my
installation of TMG and have some more things to figure out before I can
make it active (the default gateway) (found a few unsual things already
but, it is in beta afterall).

I don't know what the issue with the VPN clients was and why some worked
fine and others did not. As a side note, the TMG (ISA) server I'm testing
is in use as our new VPN server. Since I route out a different public IP
from the LAN, I was able to connect to the server externally from here at
work (out one public IP and connecting to another public IP that is the
public facing NIC of the ISA server that is running RRAS). That worked
fine. When I tried to connect to the other company's VPN service, it would
stall at 'verifying username and password' and then time out after about
30 seconds.

While I was testing this and making screen shots to send a detailed email
back down to their IT people, it just started working fine. Even though I
don't have an account with them, I know it was fine because, during my
third or forth test during screen shot taking, it prompted me to re-enter
my username password. That's when I quickly walked into the office next to
me and told the employee to try connecting right then and there and, sure
enough, everything was suddenly fine. Nothing changed on my end so I
suspect something changed on their end but I wouldn't know what and they
haven't told me otherwise.

So .. I'm lost on this one. Nothing makes much sense; there's no logic in
any of it that I can narrow things down to a cause. When some work and
others don't and their settings are the same .. I don't know which
direction to look in. If it would have been a user account issue, then
they would have been re-prompted for their username/password again just as
I was on my last 'test' before I found out it was working ok. But, that
wasn't the case.

--

"Phillip Windell" <philwindell@xxxxxxxxxxx> wrote in message
news:%23B165Wm%23JHA.3544@xxxxxxxxxxxxxxxxxxxxxxx
Jim,
If I remember correctly,..don't you use ISA Server?
If true,...has the Client that does not work recently had the Firewall
Client software installed on their machine?...the ones that do work do
not have the FWC installed (or have it disabled when the VPN is
attempted)?


--
Phillip Windell

The views expressed, are my own and not those of my employer, or
Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------


"Jim in Arizona" <tiltowait@xxxxxxxxxxx> wrote in message
news:ecdpCLm%23JHA.5092@xxxxxxxxxxxxxxxxxxxxxxx
Employees trying to connect to another location (VPN connection). Was
working fine the other day but now it is not, and yet it is working for
a few others in the same office (LAN). Nothing has changed as far as
this network but I can't speak for the network they're trying to connect
to, which is half a world away and controlled by the parent company.

When looking at the VPN connection settings for the working client and
the client that doesn't work, I see no differences in the VPN connection
setup and they (the employee) hasn't made any changes.

When the client that's not working tries to connect, all that happens is
the connection starts, and he gets to the part where it says "verifying
username and password" and it stops there, then times out after a while
with a 'no response from server'.

With the client that works, if I try a different (bad) password, the
employee is prompted to reenter his credentials. I did this just to see
if it was a password entry issue but it apparently is not.

Any ideas?

TIA,
Jim

--









.



Relevant Pages

  • Re: VPN clients unable to connect to other resources.
    ... gateway matches the IP of the remote client, and DNS and WINS point to the ... remote (although it takes close to a minute to connect, ... This is just regular Windows VPN, ... VPN server, remote routing and access running on the SBS 2003 server ...
    (microsoft.public.windows.server.sbs)
  • RE: Problems with connectcomputer and active directory
    ... I understand that you would like to join a remote client to the domain. ... If you have hardware VPN tunnel setup using Linksys or others, ... In this scenario you have to configure the SBS Server computer to enable ... Create a VPN connection to ISA/RRAS on the Internet ...
    (microsoft.public.windows.server.sbs)
  • RE: Remote connectivity problems
    ... do you mean you have added a remote client to SBS ... If you have hardware VPN tunnel setup using Linksys or others, ... In this scenario you have to configure the SBS Server computer to enable ...
    (microsoft.public.windows.server.sbs)
  • Re: VPN clients unable to connect to other resources.
    ... Are you saying that an XP Home PC wouldn't be able to connect to a server share over VPN? ... Can ping the SBS but not the client PCs on the same network. ... gateway matches the IP of the remote client, ...
    (microsoft.public.windows.server.sbs)
  • Re: Secure VPN access
    ... with it's security option for the client. ... After getting the VPN connection I check the Ip settings and found the ... point to the head ISP's DNS server. ... > Computer certificates for L2TP/IPSec VPN connections ...
    (microsoft.public.windows.server.sbs)