Re: Nortel Contivity Client works without router but not with router.



Simon <simon@xxxxxxxxxxxx> wrote:

>finite9 wrote:
>> Thanks for the tip about the pass through option in the client! I had
>> noticed that when viewing the information about the connection, when
>> connected without the router, then it would say NAT Traversal disabled.
>> I wasn't sure at the time, if it was just saying that because I wasn't
>> using NAT or because the option was turned off, thus implying that it
>> could be manually configured.
>>
>> The problem is that my client seems to be of the 'locked down' type,
>> where the company has disabled options--I have no such option in my
>> client to enable pass through, in fact there are no connection options
>> at all other than auth. and name server options, but maybe its worth a
>> shot getting a pirate copy of the full (open) client to see if the
>> option exists?
>>
>> My main problem, and the reason for searching on usenet, is that my
>> companys IT department point blank refuses to help me fixing this
>> problem because "it works fine without the router" and they "dont
>> support routers when using VPN". Totally absurd stance if you ask me.
>> This also means that I cannot get support from Nortel because you need
>> to go through your account manager: you cannot simply ask for Nortel
>> support as an end user.
>>
>> It was interesting what you said about not being able to simply open
>> port 500 for IPSec. Maybe this explains why I had to use port
>> triggering, and why it doesn't work as it should even then? If the
>> IPSec VPN option within the router is not functioning as it should with
>> this firmware, then what you say implies that I will not get this
>> working simply by enabling ports in 'port forwarding' due to the NAT
>> aspect of the connection?
>>
>> Regards,
>> Andrew
>>
>Hi,
>Sorry I can't help much on this, but that attitude of " "it works fine
>without the router" and they "dont
>support routers when using VPN". " seems totally obsurd to me, would
>they rather people were without the protection of nat/routers all the
>time they don't connect to the office then catch something and then
>connect into the corporate network ? - idiots if you ask me.
>
>Simon

The problem is that most of the cost incurred by corporate VPNs is not
the 10s of thousands spent on VPN gateways nor the $50-$100 per user
license, nor the monthly cost of the internet bandwidth consumed by
VPN usage. It is supporting the desktop user. Flat and simple. User
support for VPn is painful, I've seen these implemented by four
companies and it is still painful. Often requires users dispatched to
individual homes!! Which is a waste of hours, often to resolve basic
issues.

Many corporations now only support VPN on company issued laptops. And
saying you support routers at home means you support every cheap bad
piece of crap the market pumps out. It is a nightmare to even try.

Lastly, PC technicians know as much about netowrking and routers as
the average person does about surgery. It has nothing to do with
their field of expertise. However, everything bleeds into everything.


The same attitude can be turned around on the consumer/user.
As the user it is YOUR router. NOT theirs. WHy don't YOU know how to
make YOUR router work properly. Why does the user get to act the
helpless victim and everyone else must make the router they bought
with the ISP they choose and the PC they bought with software they
installed work with one function of a company's offering.

I've been on both sides of the issue, so i'm familiar with this
situation.
DiGiTAL_ViNYL (no email)
.



Relevant Pages

  • Re: VPN drops
    ... we can try to set up several VPN connections ... hardware (DSL router) limitation. ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • RE: NSLOOKUP: Office Conx OK Home Conx Not
    ... When a client PC is physically removed from the domain it cannot access the ... Internet unless the VPN software is running. ... IPOCONFIG shows a local ip address (from a home router). ...
    (microsoft.public.windows.server.dns)
  • VPN drops frequently
    ... I have a VPN client connection to a Watchguard SOHO 6tc firewall router ...
    (comp.security.firewalls)
  • Re: WRT54GL with DD-WRT VPN firmware - wheres the beef?
    ... the easiest way to deal with a VPN is to *FIRST* understand how ... as the NAT LAN connected to the terminating VPN server, to the client. ... Destination router: ... Gateway IP = 192.168.3.1 ...
    (alt.internet.wireless)
  • Re: WRT54GL with DD-WRT VPN firmware - wheres the beef?
    ... after the connection is established. ... the easiest way to deal with a VPN is to *FIRST* understand how ... as the NAT LAN connected to the terminating VPN server, to the client. ... Destination router: ...
    (alt.internet.wireless)