Author Topic: Network Connect Virtual adapter problems  (Read 27007 times)

zguy28

  • Newbie
  • *
  • Posts: 34
  • Karma: +0/-0
    • View Profile
Network Connect Virtual adapter problems
« on: March 05, 2008, 11:56:38 am »
I have an SA-4000 SSL VPN running ScreenOS 5.5R2.1. My Network Connect clients consistently have problems connecting after a reboot.

It seems that the NC Virtual Adapter cannot configure itself to get an IP if it has a 169 IP address (hardware address from the client Win OS). In the NC log it shows it hitting 30 retries and then quits with "Error handling config."

If I release the IP of the NC Adapter prior to connecting to the IVE it will go through the very first time.

I know its not a software or Group Policy conflict as I have stripped some of my test computers down to virtually nothing, including getting rid of AV and some miscellaneous device drivers.


zguy28

  • Newbie
  • *
  • Posts: 34
  • Karma: +0/-0
    • View Profile
Re: Network Connect Virtual adapter problems
« Reply #1 on: March 05, 2008, 12:25:37 pm »
Additional info:

the error message is: The Network Connect Session Terminated  (nc.windows.app.23712)

spacyfreak

  • Hero Member
  • *****
  • Posts: 515
  • Karma: +0/-0
    • View Profile
Re: Network Connect Virtual adapter problems
« Reply #2 on: March 05, 2008, 02:17:13 pm »
I dont understand completely - but when the clients have an 169.254 IPAddresse, they have a general network problem cause they dont have a valid DHCP IP, windows gives itself an 169.254 IP Address when DHCP Service is unavailable. Then they cannot be routed to IVE and so they can not start the vpn connection.

zguy28

  • Newbie
  • *
  • Posts: 34
  • Karma: +0/-0
    • View Profile
Re: Network Connect Virtual adapter problems
« Reply #3 on: March 06, 2008, 07:46:42 am »
The Juniper Network Connect Virtual Adapter gets a 169.254 IP, not the NIC.

Baldrick

  • Full Member
  • ***
  • Posts: 174
  • Karma: +0/-0
    • View Profile
Re: Network Connect Virtual adapter problems
« Reply #4 on: March 06, 2008, 08:37:18 am »
Does it happen for a user with local admin rights to the machine?

zguy28

  • Newbie
  • *
  • Posts: 34
  • Karma: +0/-0
    • View Profile
Re: Network Connect Virtual adapter problems
« Reply #5 on: March 06, 2008, 08:42:16 am »
Yes. Domain Admin rights even.

spacyfreak

  • Hero Member
  • *****
  • Posts: 515
  • Karma: +0/-0
    • View Profile
Re: Network Connect Virtual adapter problems
« Reply #6 on: March 06, 2008, 09:59:40 am »
Check IP Pools on Network Connect Profiles.
Do a Policy trace (Troubleshooting... Policy Trace) with a problem user pc to find out whats going on.

khan,Nabeel

  • Newbie
  • *
  • Posts: 3
  • Karma: +0/-0
    • View Profile
Re: Network Connect Virtual adapter problems
« Reply #7 on: June 04, 2008, 11:23:00 am »
Additional info:

the error message is: The Network Connect Session Terminated  (nc.windows.app.23712)
how can i solve the problem

alan

  • Hero Member
  • *****
  • Posts: 796
  • Karma: +0/-0
    • View Profile
    • paleale
Re: Network Connect Virtual adapter problems
« Reply #8 on: June 04, 2008, 12:48:15 pm »
Suggestion: instead of configuring NC to use DHCP, allocate a block of IPs for NC and route these to the IVE.

khan,Nabeel

  • Newbie
  • *
  • Posts: 3
  • Karma: +0/-0
    • View Profile
Re: Network Connect Virtual adapter problems
« Reply #9 on: June 04, 2008, 01:15:45 pm »
do you mean assign static IP and what does IVE stand for.

alan

  • Hero Member
  • *****
  • Posts: 796
  • Karma: +0/-0
    • View Profile
    • paleale
Re: Network Connect Virtual adapter problems
« Reply #10 on: June 04, 2008, 02:48:43 pm »
IVE = Instant Virtual Extranet - another name for the SSL VPN
Assign an IP pool instead of using DHCP for your NC clients. Yes, a static block.

khan,Nabeel

  • Newbie
  • *
  • Posts: 3
  • Karma: +0/-0
    • View Profile
Re: Network Connect Virtual adapter problems
« Reply #11 on: June 06, 2008, 06:06:53 am »
Dear ALAN
I made static IP and still i receive the same message any thing else i can make to sort out this error
the error message is: The Network Connect Session Terminated  (nc.windows.app.23712)
how can i solve the problem

zguy28

  • Newbie
  • *
  • Posts: 34
  • Karma: +0/-0
    • View Profile
Re: Network Connect Virtual adapter problems
« Reply #12 on: June 06, 2008, 01:18:30 pm »
I am still having the problem for some users. In addition many of my users now get error saying the NC timed out.

Various different types of internet connections and the IVE is hosted on a DS3.

JTAC can't seem to come up with any answers except "upgrade to this new OS". They even closed out my tech case without asking me.

Not the level of support you'd expect from a bunch of ex-Cisco guys.

ahd71

  • Jr. Member
  • **
  • Posts: 81
  • Karma: +1/-0
    • View Profile
Re: Network Connect Virtual adapter problems
« Reply #13 on: September 15, 2008, 06:13:35 am »
Hi,

"Bumping this thread" as this still is a problem for us. Anyone having some more information to continue the troubleshooting.

BR / ahd71

zguy28

  • Newbie
  • *
  • Posts: 34
  • Karma: +0/-0
    • View Profile
Re: Network Connect Virtual adapter problems
« Reply #14 on: September 15, 2008, 06:16:25 am »
Try changing the MTU size on your external port to 1400.

By default it is 1500.

ahd71

  • Jr. Member
  • **
  • Posts: 81
  • Karma: +1/-0
    • View Profile
Re: Network Connect Virtual adapter problems
« Reply #15 on: September 15, 2008, 06:47:49 am »
Thanks,

I changed the MTU but i got error 23712 with a 1400 MTU too.

I get error 23712 one out of ten connection attempts approximately and is running 5.5R7 from Windows Vista.

BR / ahd71

BR / ahd71

zguy28

  • Newbie
  • *
  • Posts: 34
  • Karma: +0/-0
    • View Profile
Re: Network Connect Virtual adapter problems
« Reply #16 on: September 18, 2008, 06:04:03 am »
Some of my clients still have problems sometimes. Apparently it is their Cable or DSL ISP.

Also Wifi is notoriously bad for these issues as well.