Network Connect Issue

[dw-ecl_]

Hope someone can help. I have a machine which is connecting to the network using Network Connect v5.5 r7. When I click on the Start button to fire up Network Connect it takes an age to actually start up and connect (around 60-90 seconds) and I start getting errors in the event log about the DHCP server denying the request for an IP address and DNS entries not being updated. I have other machines that use Network Connect and it starts up within seconds for them.

Also, when Network Connect finally does connect I can no longer browse the Internet - that stops working until I sign out.

Hope someone has some ideas?

Thanks,

D

[cbarcellos_]

Check to see if a software based firewall, AV, antispyware/malware, or other similar app is causing the issue.

disable all of those, and then retry.

If needed, take a www.belarc.com report on both a working and broken system and see what applications differ from machine to machine. It sounds like you are experiencing some kind of application confliction.

[dw-ecl_]

Thanks for the reply. I have done a bit of testing on the machine and have found that the problem with Network Connect taking a long time to connect only seemt to happen if the user on the machine is not a local admin. I am an admin on all machines and when I try to connect it works fine. A bit bizarre, not sure if this is an issue that has been noticed before?

Thanks,

D

[rdit_]

what is configured for the NC connection? NCP (means just SSL) or ESP? ESP should be faster and if it fails (for example because of not having udp/4500 at firewalls opened) it automatically falls back to NCP. so you could just try to change this setting, that should increase performance.

you have a really old version, did you think about upgrading it? could also solve your problem

[MattS_]

Are you also using the same credentials to sign into the SA as the user and getting mapped to the same roles?

As you find that with Admin priveleges the NC works fine, I'd suggest uninstalling NC and then installing the Juniper Installer Service from the Maintenance >System > Installers page as an admin user. This will allow non-admin users to be able to install and upgrade NC and other components.

[dw-ecl_]

Many thanks for the replies.

I initially did think that security software may be causing the issue but if that was the case then the problem would occur for all users.

The Network Connect connection is already set to ESP. I do need to do an upgrade to the latest version at some point, I just need to schedule in a time to do it.

If I log onto the laptop I can log onto the SA as any user and start up Network Connect fine. I can also stil browse the Internet OK. However the problems all start occuring again when logged on as a standard user. I have tried uninstalling NC, then installing the Juniper Installer Service. I then tries to use Network Connect as a standard user and it installed fine but I am still getting the same problems.

Do not know if this will help, if I do a tracert when I have connected to NC successfully the first device it hits has an address of 10.200.200.200 (which it thinks is the DHCP server), it then hits the corporate default gateway and then the corporate firewall and then various routers.

If I try the same tracert when I have finally connected to NC as a standard user it gets to the 10.200.200.200 address and then no further?

Thanks,

D

[dw-ecl_]

Many thanks for the replies.

I initially did think that security software may be causing the issue but if that was the case then the problem would occur for all users.

The Network Connect connection is already set to ESP. I do need to do an upgrade to the latest version at some point, I just need to schedule in a time to do it.

If I log onto the laptop I can log onto the SA as any user and start up Network Connect fine. I can also stil browse the Internet OK. However the problems all start occuring again when logged on as a standard user. I have tried uninstalling NC, then installing the Juniper Installer Service. I then tries to use Network Connect as a standard user and it installed fine but I am still getting the same problems.

Do not know if this will help, if I do a tracert when I have connected to NC successfully the first device it hits has an address of 10.200.200.200 (which it thinks is the DHCP server), it then hits the corporate default gateway and then the corporate firewall and then various routers.

If I try the same tracert when I have finally connected to NC as a standard user it gets to the 10.200.200.200 address and then no further?

Thanks,

D

[dw-ecl_]

OK, think that I have figured out what the problem is - it seems to be something to do with our proxy server. Currently users have their IE pointing to a wpad file and are not able to change those settings. If I do a bit of tinkering and remove those IE settings so that they are not pointing to the wpad file and therefore not going through the proxy server everything works fine.

I don't suppose anyone knows how to get round this do they?

Many thanks,

D