Re: VPN problem with AT&T Global VPN





In news:EA943934-574C-43AF-9F9A-77E106D304B5@xxxxxxxxxxxxx,
Preston <Preston@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
Thank you for the quick answer. No I do not have ISA installed or
configured. This application actually goes out to the AT&T VPN site
and then tries to make a connection back to the workstation through
the internet. Not sure exactly how it works as it is associated with
some type of Medical billing information. I think my problem is
somewhere in having the two network cards in the server configured as
a firewall. I like your answer about good firewall. Have had good
luck with Sonicwall and will try to get client to buy that. Any help
in the meantime on the two network cards in the server would be
appreciated.

Sorry, I never use that config, so I can't really help you...perhaps someone
else will post. Again, I'd be concerned that the workstation would lose
connectivity to the company network while the tunnel was active - you should
probably look into this.

Thanks

Preston

"Lanwench [MVP - Exchange]" wrote:



In news:3ECE82E5-58CF-43F9-90AA-E939A4E42B82@xxxxxxxxxxxxx,
Preston <Preston@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
I have Windows 2003 Small Business Server fully patched and
configured with 2 network cards and a Cayman DSL Router. We are
trying to use a product that requires the user to run the AT&T
Global VPN on their workstation which goes out to their site and
attempts to make a VPN connection. When it is run, they get an
error 118 during authentication process. I have run the Internet
Connection Wizard and completly turned off the Server Firewall, but
still can't get it to work. I can connect the workstation directly
to the DSL Router and it works fine, but not through the Server.
Any suggestions?

Are you using ISA? (I don't know how you'd *fix* this in ISA, but
I'm sure someone will).

I'd be a little worried about a VPN client on a workstation like
this - if it's set up to deny all outbound connections that don't go
out through the tunnel, once that's established, your users won't be
able to do anything on your own server/network. I haven't had good
luck with this myself.

Also - if you aren't using ISA, get yourself a good hardware firewall
appliance.


.



Relevant Pages

  • Re: Connecting a remote workstation to a domain
    ... created the VPN connection and tested with the same results from a remote ... login, then log out and try the "log on using dialup connnection". ... She has been using VPN for over a year ... woremote workstation. ...
    (microsoft.public.windows.server.sbs)
  • Re: Connecting a remote workstation to a domain
    ... she is granted VPN rights to the SBS server)? ... Even setting up a low end workstation in the ... I have also selected not to dial an initial connection before ... remark that you will have to reboot the workstation. ...
    (microsoft.public.windows.server.sbs)
  • Re: Connecting a remote workstation to a domain
    ... VPN for "All Users" to the SBS server (and using her domain credentials). ... created the VPN connection and tested with the same results from a remote ... Even setting up a low end workstation ...
    (microsoft.public.windows.server.sbs)
  • Re: Connecting a remote workstation to a domain
    ... Log onto the laptop with her domain credentials without using the VPN at ... login, then log out and try the "log on using dialup connnection". ... I have also selected not to dial an initial connection ... woremote workstation. ...
    (microsoft.public.windows.server.sbs)
  • Re: Internet Access from LAN
    ... In your IP config for the workstation... ... Ethernet adapter Local Area Connection: ... a Win2K Pro machine via a registry edit (and tow NICs installed in it). ...
    (microsoft.public.windows.server.sbs)

Loading