CPUG

The Check Point User Group

A Resource For The Check Point Community.  Fast.  Useful.  Independent.

1. CCSA/CCSE One-Week Dual-Certification Training Course with CPUG in San Francisco!
    Courses Starting 12/8, (2009) 1/19, 2/9, 3/9, 4/6, 5/4, 6/8, 7/6, 8/3.
2. Join Us On LinkedIn - We now have a CPUG group.


Go Back   CPUG: The Check Point User Group > Check Point Firewall-1/VPN-1 Platforms > Check Point VPN-1 Edge Appliances
Assigned IP failed? Assigned IP failed?
Register FAQ Members List Calendar Search Today's Posts Mark Forums Read

Reply
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 2006-09-02
Junior Member
  
Join Date: 2006-09-02
Posts: 1
Rep Power: 0
jpk79 has an average reputation (10+)
Default Assigned IP failed?
I have my VPN-1 Edge VPN server enabeld for users to connect to internal networks. I can get connected OK, however I can not reach any destinations on my internal network. My SecurClient says the Assigned IP failed? Anyone know why this is? Thanks.
Reply With Quote
  #2 (permalink)  
Old 2006-10-03
Junior Member
  
Join Date: 2006-10-03
Posts: 1
Rep Power: 0
gavin.morris@agilisys.co. has an average reputation (10+)
Default Re: Assigned IP failed?
Has anyone else experienced this? I have the exact same issue. On 2 seperate laptops. using the same SecuRemote client, and the same VPN certificate, one laptop is able to connect, authenticate and obtain an IP address.

The other client, is able to connect, authenticate but is unable to obtain an IP address. When I go into the advanced tab of the SecuRemote client, and click on connection details, under status summary it says Assigned IP Failed and under Office Mode it says the same.

Help!
Gavin
London
Reply With Quote
  #3 (permalink)  
Old 2006-10-03
Junior Member
  
Join Date: 2006-09-27
Posts: 12
Rep Power: 0
theoracle has an average reputation (10+)
Default Re: Assigned IP failed?
Try increasing the MTU Tunnel size on the SecureClient machine's network adapter. If you are running the client on a Windows Platform, then it can be changed in your Network Connections, TCPIP Properties tab. No guarantees, but this resolved a very similiar issue I have experienced with previous versions of the SecureClient. HKeyLocalMachine\System\CurrentControlSet\Services \Tcpip\Parameters\Interfaces\Adapter Number ---> Change Value Data: 0xffffffff for Value Name: MTU
Reply With Quote
Reply

« Previous Thread | Next Thread »
Thread Tools
Display Modes
Linear Mode Linear Mode

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are Off
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


All times are GMT -7. The time now is 05:06.

Contact Us - CPUG Home Page - Archive - Top

Powered by vBulletin® Version 3.7.4
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.2.0