cancel
Showing results for 
Search instead for 
Did you mean: 

Pulse Client takes very long to connect after Sleep

format_c_
Not applicable

Pulse Client takes very long to connect after Sleep

Hi folks,

I've made the experience that the Pulse Client under certain circumstances takes very long to establish a connection using location awareness.

It's being tested on Windows7 when the computer is being recovered from sleep state.

You can see that Pulse is detecting Internet connectivity and initiates the connection immediately.

Then it just remains in this state for 2,5 minutes and then surpisingly connects as expected without any complaints.

Just a second before the connection succeeds, you can hear a sound like pluggin in a device (s.a. USB-Stick or USB Mouse).

Until this sound can be heard the following messages can be found in the Logfile (VAMGR).

00171,09 2011/04/20 23:47:15.006 1 SYSTEM dsAccessService.exe dsTMService p2124 t1ED4 VaDeviceControl.cpp:199 - 'VAMGR' --C_VaDeviceControl:Smiley FrustratedtartHardware()[0]:IoControl failed 0
00180,09 2011/04/20 23:47:15.006 1 SYSTEM dsAccessService.exe dsTMService p2124 t1ED4 VaDeviceControl.cpp:205 - 'VAMGR' --C_VaDeviceControl:Smiley FrustratedtartHardware()[0]:CancelIo failed 1, abort...
00171,09 2011/04/20 23:47:40.008 1 SYSTEM dsAccessService.exe dsTMService p2124 t1ED4 VaDeviceControl.cpp:199 - 'VAMGR' --C_VaDeviceControl:Smiley FrustratedtartHardware()[0]:IoControl failed 0
00180,09 2011/04/20 23:47:40.008 1 SYSTEM dsAccessService.exe dsTMService p2124 t1ED4 VaDeviceControl.cpp:205 - 'VAMGR' --C_VaDeviceControl:Smiley FrustratedtartHardware()[0]:CancelIo failed 1, abort...
00171,09 2011/04/20 23:48:05.011 1 SYSTEM dsAccessService.exe dsTMService p2124 t1ED4 VaDeviceControl.cpp:199 - 'VAMGR' --C_VaDeviceControl:Smiley FrustratedtartHardware()[0]:IoControl failed 0
00180,09 2011/04/20 23:48:05.011 1 SYSTEM dsAccessService.exe dsTMService p2124 t1ED4 VaDeviceControl.cpp:205 - 'VAMGR' --C_VaDeviceControl:Smiley FrustratedtartHardware()[0]:CancelIo failed 1, abort...
00169,09 2011/04/20 23:48:15.011 1 SYSTEM dsAccessService.exe dsTMService p2124 t1ED4 ManagerVA.cpp:121 - 'TM' setAdapterMediaConnectStatus failed (0x746af40), error=1, retry=3
00134,09 2011/04/20 23:48:15.011 3 SYSTEM dsAccessService.exe dsTMService p2124 t1ED4 ManagerVA.cpp:640 - 'TM' jvaReleaseRef(), VA(0x746af40)
00152,09 2011/04/20 23:48:15.011 1 SYSTEM dsAccessService.exe ncAccessMethod p2124 t1ED4 ncAdapter.cpp:580 - 'ncAmAdapter' Can't enable TM Inteface: -536870911


I don't really think this is an issue with the Junos Pulse Client.
But I think you have made many experiences within many environments and maybe have seen this behaviour before.
Does somebody have an idea if it's possible to shorten or eliminate that "waiting" period? Maybe by applying a certain Microsoft Patch. Thank you guys in advance.

Cheers Alex

1 REPLY 1
OKCubsFan_
New Contributor

Re: Pulse Client takes very long to connect after Sleep

I'm experiencing the exact same issues in our environment. Our deputies are complaining about having to reboot their PC's in order to get Pulse to work again. Typically, this problem arises after the PC is in a dormant phase (hibernation, sleep mode) for over 15 minutes. Is there any way to tweak the Pulse client timeout options?