VPN over UMTS
Hi guys !
I'm not sure if the USA group can give any input to this or if I have a
somehow European problem as it's related to a UMTS connection. Our company
has some "try and buy" UMTS boxes from the German provider T-Mobile. In the
default configuration, they assign private IP addresses and apparently do
NAT for Internet access. In this setup, the Cisco VPN client does not work
but as soon as I'm requesting a public address (this can be done in the
software), things work fine.
Does anybody know why it doesn't work with the private address and NAT? It
should be quite the same as with NAT behind a DSL router (which also
works), shouldn't it? We'd prefer the NAT thing fort security reasons.
TIA
fw
.
Relevant Pages
- Re: VPN over UMTS
... somehow European problem as it's related to a UMTS connection. ... has some "try and buy" UMTS boxes from the German provider T-Mobile. ... the Cisco VPN client does not work ... Does anybody know why it doesn't work with the private address and NAT? ...
(comp.dcom.sys.cisco) - Re: NAT without DHCP? (w2k3)
... How I can troubleshoot the problem and see why ip packets from the private ... DNS works perfectly fine but nothing else. ... How does your server connect to the Internet? ... I also enabled NAT tracing - may be this can help? ...
(microsoft.public.windows.server.networking) - Re: NAT without DHCP? (w2k3)
... is that dialog to configure address pool for the private network? ... (Just to add to the confusion there is another pool of addresses in RRAS ... If you want to use it, you configure a pool of IP addresses for NAT ... is enabled on the public interface of the RRAS server already. ...
(microsoft.public.windows.server.networking) - Re: NAT and RDP ?
... NAT device from a Client on the private side of the LAN. ... If the Resource is bound only to the Public IP# of the Server (like IIS can do ...
(microsoft.public.windows.server.networking) - Re: RRAS Win2003: Cannot reach public IP reserved hosts behind our NAT
... From within our intranet we can access the machines by> their private addresses just fine, as these packets are not> routed to our RRAS box. ... The role of the IP# in Ethernet is only to provide a Layer3 routing> mechanism and to provide a means to resolve the MAC address. ... The> reason intranet host must use the private addresses to access the servers is> because NAT can't make "u-turns". ... When you send a packet to the external> IP# the "NAT" process takes it and creates a situation where the source and> destination MAC addresses in the packet headers are the same address. ...
(microsoft.public.windows.server.networking) |
|
