My Passport Essential constant connect disconnect on some windows 8.1 machines

Hi All, I have a 500 GB My Passport Essential, it works fine on my win 7 laptop, and my win 8.1 laptop, but on my win 8.1 pc that I recently built it constantly connect and disconnects. I have tried disabling the hard drive sleep mode settings in power settings, tried using WD Drive Utilities on Win 7 but it wouldnt recognise the drive. Turning off the sleep mode settings did make it show up for a very short while, but after that it was back to connecting and disconnecting. The hdd light turns on, I can hear the drive spinning, and I can hear the connect/disconnect sounds from windows. Any ideas?

Hi, welcome to the community.
It seems might be a power issue or the USB port in the board. Have you tried using another port and another cable? Also making sure in the power settings that the USB are not set to be turned off.

Similar Messages

Ipod keeps connecting & disconnecting

whenever i connect my ipod 2 my computer it keeps connecting & disconnecting over & over again. what is wrong?

I solved the constant connection/disconnection problem on my 4G iPod Nano by buying a Belkins 5 port PCI USB Card Model FSU220 and connecting my iPod to this card rather than the on board USB. The Belkins card uses a NEC USB controller chip. I believe the constant connection/disconnection problem is caused when a VIA Chip is used as the USB Controller. If you are having this problem you probably have a VIA USB controller.
Although other cards with other controllers might solve the problem I bought this one because it was available locally (about $35.00 at Staples) and it is Mac and Windows compatible.
I tried restarting the computer, re-installing iTunes, connecting to a different USB plug, and returning the iPod for another and nothing worked. Installing the card solved the problem for me.
Interesting to note that my previous ipod classic worked on the computer's built-in USB plugs without any problems. Also interesting is that I could keep the iPod connected to the computer and transfer files to the iPod (not music files) as long as iTunes was not running.

AnyConnect pre Windows login connects and disconnects for some users

Hi,
I have Cisco VPN AnyConnect (version 3.1.0310) clients with a connectivity issue which manifests as follows:
A user boots their Windows 7 SP1 laptop up.
Before Windows login, the user clicks "switch user" and enters their Cisco AnyConnect credentials (this connects OK).
Once the VPN tunnel is established a user logs into Windows.
At this point, 1 of 2 things happen:
1. Most users VPN connection stays connected and user GPO processing\logins work as normal
2. For a minority of users, the VPN connection disconnects and then reconnects. The VPN disconnect and reconnect causes connectivity issues with mapped drives and Outlook (most likely due to GPO processing not applying as the VPN tunnel wasn't established at the required time).
There are no known commanalities between problematic users - all users are in the same OU and laptops are in the same OU, so they should be getting the same AD settings. The same user can login 14 times OK, but may experience this issue on the 15th occasion.
Within the profile xml file (stored in c:\program data\) the key "AutoConnectStart" is set to false for user controllable and default value. The XML policy settings are being applied correctly (we've checked Event ID 3010 within the Cisco AnyConnect Windows logs).
What we have noticed from using the back end Cisco monitoring client is that users who experience connection issues, connect pre windows login OK, but once they're logged into Windows the Cisco VPN AnyConnects seems to try and re-connect, which causes the current VPN tunnel to disconnect and re-connect. This disconnect and re-connect for users seems to cause issues with logon and GPO processing.
So far, the only rock solid way we've found of stopping this disconnect and re-connect behaviour is by configuring a system deny permission on registry key "HKLM\Software\Microsoft\Windows\CurrentVersion\Run". This key contains an entry for Cisco AnyConnect VPN. Unfortunately setting a deny on the individual node value isn't possible and if the key is deleted or modified the system re-creates it. I'd rather avoid setting a system deny on the key for all users.
Any advice on how troubleshoot and diagnose this problem is appreciated.
Thanks

I've attached some log files in case someone is particularly keen eyed at spotting issues (all data is anonymized)
6
Oct 30 2013
10:19:31
172.16.12.17
58124
10.5.128.21
8080
Built inbound TCP connection 123678229 for outside:172.16.12.17/58124 (172.16.12.17/58124)(LOCAL\jpk789) to inside:10.5.128.21/8080 (10.5.128.21/8080)
6
Oct 30 2013
10:19:31
172.16.12.17
58122
10.5.140.210
443
Teardown TCP connection 123678214 for outside:172.16.12.17/58122(LOCAL\jpk789) to inside:10.5.140.210/443 duration 0:00:00 bytes 11971 TCP Reset-O
6
Oct 30 2013
10:19:31
172.16.12.17
51368
10.5.141.155
53
Teardown UDP connection 123678191 for outside:172.16.12.17/51368(LOCAL\jpk789) to inside:10.5.141.155/53 duration 0:00:00 bytes 110
6
Oct 30 2013
10:19:31
172.16.12.17
58123
10.5.12.182
88
Built inbound TCP connection 123678217 for outside:172.16.12.17/58123 (172.16.12.17/58123)(LOCAL\jpk789) to inside:10.5.12.182/88 (10.5.12.182/88)
6
Oct 30 2013
10:19:31
172.16.12.17
62455
10.5.141.155
53
Teardown UDP connection 123678189 for outside:172.16.12.17/62455(LOCAL\jpk789) to inside:10.5.141.155/53 duration 0:00:00 bytes 430
6
Oct 30 2013
10:19:31
172.16.12.17
58122
10.5.140.210
443
Built inbound TCP connection 123678214 for outside:172.16.12.17/58122 (172.16.12.17/58122)(LOCAL\jpk789) to inside:10.5.140.210/443 (10.5.140.210/443)
6
Oct 30 2013
10:19:31
172.16.12.17
56197
10.5.141.155
53
Built inbound UDP connection 123678212 for outside:172.16.12.17/56197 (172.16.12.17/56197)(LOCAL\jpk789) to inside:10.5.141.155/53 (10.5.141.155/53)
6
Oct 30 2013
10:19:31
172.16.12.17
58121
10.5.12.179
389
Built inbound TCP connection 123678196 for outside:172.16.12.17/58121 (172.16.12.17/58121)(LOCAL\jpk789) to inside:10.5.12.179/389 (10.5.12.179/389)
6
Oct 30 2013
10:19:31
172.16.12.17
58120
10.5.12.199
80
Built inbound TCP connection 123678195 for outside:172.16.12.17/58120 (172.16.12.17/58120)(LOCAL\jpk789) to inside:10.5.12.199/80 (10.5.12.199/80)
6
Oct 30 2013
10:19:31
172.16.12.17
51368
10.5.141.155
53
Built inbound UDP connection 123678191 for outside:172.16.12.17/51368 (172.16.12.17/51368)(LOCAL\jpk789) to inside:10.5.141.155/53 (10.5.141.155/53)
6
Oct 30 2013
10:19:31
172.16.12.17
62458
10.5.12.182
389
Built inbound UDP connection 123678190 for outside:172.16.12.17/62458 (172.16.12.17/62458)(LOCAL\jpk789) to inside:10.5.12.182/389 (10.5.12.182/389)
6
Oct 30 2013
10:19:31
172.16.12.17
62455
10.5.141.155
53
Built inbound UDP connection 123678189 for outside:172.16.12.17/62455 (172.16.12.17/62455)(LOCAL\jpk789) to inside:10.5.141.155/53 (10.5.141.155/53)
6
Oct 30 2013
10:19:30
IPSEC: An inbound remote access SA (SPI= 0x67ED9B28) between 80.21.182.245 and 75.12.34.56 (user= jpk789) has been created.
6
Oct 30 2013
10:19:30
IPSEC: An outbound remote access SA (SPI= 0x9C00507E) between 80.21.182.245 and 75.12.34.56 (user= jpk789) has been created.
6
Oct 30 2013
10:19:30
Group User IP <75.12.34.56> AnyConnect session resumed connection from IP <75.12.34.56>.
5
Oct 30 2013
10:19:30
Local:80.21.182.245:4500 Remote:75.12.34.56:62457 Username:jpk789 SA UP. Reason: New Connection Established
4
Oct 30 2013
10:19:30
Local:80.21.182.245:4500 Remote:75.12.34.56:62457 Username:jpk789 Warning Configuration Payload request for attribute 0x7041 could not be processed. Error: Unknown/Unsupported Attribute
4
Oct 30 2013
10:19:30
Local:80.21.182.245:4500 Remote:75.12.34.56:62457 Username:jpk789 Warning Configuration Payload request for attribute 0x7040 could not be processed. Error: Unknown/Unsupported Attribute
4
Oct 30 2013
10:19:30
Local:80.21.182.245:4500 Remote:75.12.34.56:62457 Username:jpk789 Warning Configuration Payload request for attribute 0x703f could not be processed. Error: Unknown/Unsupported Attribute
4
Oct 30 2013
10:19:30
Local:80.21.182.245:4500 Remote:75.12.34.56:62457 Username:jpk789 Warning Configuration Payload request for attribute 0x703e could not be processed. Error: Unknown/Unsupported Attribute
4
Oct 30 2013
10:19:30
Local:80.21.182.245:4500 Remote:75.12.34.56:62457 Username:jpk789 Warning Configuration Payload request for attribute 0x703d could not be processed. Error: Unknown/Unsupported Attribute
4
Oct 30 2013
10:19:30
Local:80.21.182.245:4500 Remote:75.12.34.56:62457 Username:jpk789 Warning Configuration Payload request for attribute 0x703c could not be processed. Error: Unknown/Unsupported Attribute
4
Oct 30 2013
10:19:30
Local:80.21.182.245:4500 Remote:75.12.34.56:62457 Username:jpk789 Warning Configuration Payload request for attribute 0x703b could not be processed. Error: Unknown/Unsupported Attribute
6
Oct 30 2013
10:19:18
172.16.12.17
64287
10.5.12.182
445
Teardown TCP connection 123673186 for outside:172.16.12.17/64287(LOCAL\jpk789) to inside:10.5.12.182/445 duration 0:02:01 bytes 14605 Tunnel has been torn down
6
Oct 30 2013
10:19:17
172.16.12.17
64278
10.5.141.144
445
Teardown TCP connection 123672510 for outside:172.16.12.17/64278(LOCAL\jpk789) to inside:10.5.141.144/445 duration 0:02:15 bytes 9237 Tunnel has been torn down
6
Oct 30 2013
10:19:14
172.16.12.17
64273
10.5.140.231
445
Teardown TCP connection 123672368 for outside:172.16.12.17/64273(LOCAL\jpk789) to inside:10.5.140.231/445 duration 0:02:16 bytes 7297 Tunnel has been torn down
6
Oct 30 2013
10:19:04
172.16.12.17
54449
10.5.141.155
389
Teardown UDP connection 123672541 for outside:172.16.12.17/54449(LOCAL\jpk789) to inside:10.5.141.155/389 duration 0:02:01 bytes 366
6
Oct 30 2013
10:19:04
172.16.12.17
137
10.5.141.155
137
Teardown UDP connection 123672421 for outside:172.16.12.17/137(LOCAL\jpk789) to inside:10.5.141.155/137 duration 0:02:04 bytes 486
6
Oct 30 2013
10:19:00
172.16.12.17
138
10.5.141.155
138
Teardown UDP connection 123672424 for outside:172.16.12.17/138(LOCAL\jpk789) to inside:10.5.141.155/138 duration 0:02:01 bytes 177
6
Oct 30 2013
10:18:58
172.16.12.17
63666
10.5.141.155
389
Teardown UDP connection 123672316 for outside:172.16.12.17/63666(LOCAL\jpk789) to inside:10.5.141.155/389 duration 0:02:01 bytes 366
6
Oct 30 2013
10:18:58
172.16.12.17
53105
10.5.141.155
389
Teardown UDP connection 123672300 for outside:172.16.12.17/53105(LOCAL\jpk789) to inside:10.5.141.155/389 duration 0:02:01 bytes 366
6
Oct 30 2013
10:18:47
172.16.12.17
61715
10.5.12.182
389
Teardown UDP connection 123671945 for outside:172.16.12.17/61715(LOCAL\jpk789) to inside:10.5.12.182/389 duration 0:02:01 bytes 312
6
Oct 30 2013
10:18:43
172.16.12.17
54262
10.5.12.179
389
Teardown UDP connection 123671801 for outside:172.16.12.17/54262(LOCAL\jpk789) to inside:10.5.12.179/389 duration 0:02:01 bytes 355
6
Oct 30 2013
10:18:42
172.16.12.17
57911
10.5.141.156
389
Teardown UDP connection 123671777 for outside:172.16.12.17/57911(LOCAL\jpk789) to inside:10.5.141.156/389 duration 0:02:01 bytes 365
6
Oct 30 2013
10:18:40
172.16.12.17
123
10.5.12.182
123
Teardown UDP connection 123671670 for outside:172.16.12.17/123(LOCAL\jpk789) to inside:10.5.12.182/123 duration 0:02:01 bytes 136
6
Oct 30 2013
10:18:40
172.16.12.17
58107
10.5.12.179
389
Teardown UDP connection 123671639 for outside:172.16.12.17/58107(LOCAL\jpk789) to inside:10.5.12.179/389 duration 0:02:01 bytes 356
6
Oct 30 2013
10:18:40
172.16.12.17
58825
10.5.12.179
389
Teardown UDP connection 123671633 for outside:172.16.12.17/58825(LOCAL\jpk789) to inside:10.5.12.179/389 duration 0:02:02 bytes 355
6
Oct 30 2013
10:18:39
172.16.12.17
60424
10.5.141.156
389
Teardown UDP connection 123671611 for outside:172.16.12.17/60424(LOCAL\jpk789) to inside:10.5.141.156/389 duration 0:02:01 bytes 365
6
Oct 30 2013
10:18:38
172.16.12.17
56635
10.5.141.156
389
Teardown UDP connection 123671566 for outside:172.16.12.17/56635(LOCAL\jpk789) to inside:10.5.141.156/389 duration 0:02:01 bytes 365
6
Oct 30 2013
10:18:38
172.16.12.17
61204
10.5.12.179
389
Teardown UDP connection 123671558 for outside:172.16.12.17/61204(LOCAL\jpk789) to inside:10.5.12.179/389 duration 0:02:01 bytes 355
6
Oct 30 2013
10:18:38
172.16.12.17
50615
10.5.12.179
389
Teardown UDP connection 123671545 for outside:172.16.12.17/50615(LOCAL\jpk789) to inside:10.5.12.179/389 duration 0:02:01 bytes 355
6
Oct 30 2013
10:18:38
172.16.12.17
57940
10.5.141.154
389
Teardown UDP connection 123671537 for outside:172.16.12.17/57940(LOCAL\jpk789) to inside:10.5.141.154/389 duration 0:02:02 bytes 313
6
Oct 30 2013
10:18:38
172.16.12.17
57939
10.5.141.156
389
Teardown UDP connection 123671536 for outside:172.16.12.17/57939(LOCAL\jpk789) to inside:10.5.141.156/389 duration 0:02:02 bytes 366
6
Oct 30 2013
10:18:38
172.16.12.17
64495
10.5.12.182
389
Teardown UDP connection 123671532 for outside:172.16.12.17/64495(LOCAL\jpk789) to inside:10.5.12.182/389 duration 0:02:02 bytes 356
6
Oct 30 2013
10:18:37
172.16.12.17
62965
10.5.12.182
389
Teardown UDP connection 123671521 for outside:172.16.12.17/62965(LOCAL\jpk789) to inside:10.5.12.182/389 duration 0:02:01 bytes 356
6
Oct 30 2013
10:18:37
172.16.12.17
54994
10.5.12.179
389
Teardown UDP connection 123671514 for outside:172.16.12.17/54994(LOCAL\jpk789) to inside:10.5.12.179/389 duration 0:02:01 bytes 356
6
Oct 30 2013
10:18:37
172.16.12.17
54993
10.5.12.179
389
Teardown UDP connection 123671513 for outside:172.16.12.17/54993(LOCAL\jpk789) to inside:10.5.12.179/389 duration 0:02:01 bytes 356
6
Oct 30 2013
10:18:37
172.16.12.17
63390
10.34.140.104
389
Teardown UDP connection 123671483 for outside:172.16.12.17/63390(LOCAL\jpk789) to inside:10.34.140.104/389 duration 0:02:01 bytes 385
6
Oct 30 2013
10:18:37
172.16.12.17
63389
10.33.140.104
389
Teardown UDP connection 123671482 for outside:172.16.12.17/63389(LOCAL\jpk789) to inside:10.33.140.104/389 duration 0:02:01 bytes 384
6
Oct 30 2013
10:18:10
IPSEC: An inbound remote access SA (SPI= 0x5650EE30) between 75.12.34.56 and 80.21.182.245 (user= jpk789) has been deleted.
6
Oct 30 2013
10:18:10
IPSEC: An outbound remote access SA (SPI= 0x42DBDD66) between 80.21.182.245 and 75.12.34.56 (user= jpk789) has been deleted.
6
Oct 30 2013
10:18:10
Group User IP <75.12.34.56> AnyConnect session lost connection. Waiting to resume.
5
Oct 30 2013
10:18:10
Local:80.21.182.245:4500 Remote:75.12.34.56:57103 Username:jpk789 SA DOWN. Reason: peer lost
6
Oct 30 2013
10:17:42
172.16.12.17
64250
10.5.141.186
445
Teardown TCP connection 123671908 for outside:172.16.12.17/64250(LOCAL\jpk789) to inside:10.5.141.186/445 duration 0:00:57 bytes 454851 TCP Reset-I
6
Oct 30 2013
10:17:20
172.16.12.17
137
172.16.13.255
137
Teardown UDP connection 123673268 for outside:172.16.12.17/137(LOCAL\jpk789) to outside:172.16.13.255/137 duration 0:00:00 bytes 0
6
Oct 30 2013
10:17:19
172.16.12.17
137
172.16.13.255
137
Teardown UDP connection 123673244 for outside:172.16.12.17/137(LOCAL\jpk789) to outside:172.16.13.255/137 duration 0:00:00 bytes 0
6
Oct 30 2013
10:17:18
172.16.12.17
137
172.16.13.255
137
Teardown UDP connection 123673218 for outside:172.16.12.17/137(LOCAL\jpk789) to outside:172.16.13.255/137 duration 0:00:00 bytes 0
6
Oct 30 2013
10:16:36
172.16.12.17
63060
10.5.141.155
53
Built inbound UDP connection 123671551 for outside:172.16.12.17/63060 (172.16.12.17/63060)(LOCAL\jpk789) to inside:10.5.141.155/53 (10.5.141.155/53)
6
Oct 30 2013
10:16:36
172.16.12.17
63010
10.5.12.182
88
Built inbound TCP connection 123671549 for outside:172.16.12.17/63010 (172.16.12.17/63010)(LOCAL\jpk789) to inside:10.5.12.182/88 (10.5.12.182/88)
6
Oct 30 2013
10:16:36
172.16.12.17
63009
10.5.12.182
88
Built inbound TCP connection 123671548 for outside:172.16.12.17/63009 (172.16.12.17/63009)(LOCAL\jpk789) to inside:10.5.12.182/88 (10.5.12.182/88)
6
Oct 30 2013
10:16:36
172.16.12.17
63008
10.5.141.156
389
Built inbound TCP connection 123671546 for outside:172.16.12.17/63008 (172.16.12.17/63008)(LOCAL\jpk789) to inside:10.5.141.156/389 (10.5.141.156/389)
6
Oct 30 2013
10:16:36
172.16.12.17
50615
10.5.12.179
389
Built inbound UDP connection 123671545 for outside:172.16.12.17/50615 (172.16.12.17/50615)(LOCAL\jpk789) to inside:10.5.12.179/389 (10.5.12.179/389)
6
Oct 30 2013
10:16:36
172.16.12.17
63007
10.5.12.182
88
Built inbound TCP connection 123671544 for outside:172.16.12.17/63007 (172.16.12.17/63007)(LOCAL\jpk789) to inside:10.5.12.182/88 (10.5.12.182/88)
6
Oct 30 2013
10:16:36
172.16.12.17
55425
10.5.141.155
53
Teardown UDP connection 123671487 for outside:172.16.12.17/55425(LOCAL\jpk789) to inside:10.5.141.155/53 duration 0:00:00 bytes 164
6
Oct 30 2013
10:16:36
172.16.12.17
50614
10.5.141.155
53
Built inbound UDP connection 123671543 for outside:172.16.12.17/50614 (172.16.12.17/50614)(LOCAL\jpk789) to inside:10.5.141.155/53 (10.5.141.155/53)
6
Oct 30 2013
10:16:35
172.16.12.17
56263
10.5.141.156
53
Built inbound UDP connection 123671461 for outside:172.16.12.17/56263 (172.16.12.17/56263)(LOCAL\jpk789) to inside:10.5.141.156/53 (10.5.141.156/53)
6
Oct 30 2013
10:16:35
172.16.12.17
60708
10.5.141.155
53
Built inbound UDP connection 123671460 for outside:172.16.12.17/60708 (172.16.12.17/60708)(LOCAL\jpk789) to inside:10.5.141.155/53 (10.5.141.155/53)
6
Oct 30 2013
10:16:35
172.16.12.17
56982
10.5.141.156
53
Built inbound UDP connection 123671459 for outside:172.16.12.17/56982 (172.16.12.17/56982)(LOCAL\jpk789) to inside:10.5.141.156/53 (10.5.141.156/53)
6
Oct 30 2013
10:16:35
172.16.12.17
64548
10.5.141.155
53
Built inbound UDP connection 123671458 for outside:172.16.12.17/64548 (172.16.12.17/64548)(LOCAL\jpk789) to inside:10.5.141.155/53 (10.5.141.155/53)
6
Oct 30 2013
10:16:35
172.16.12.17
60827
10.5.141.156
53
Built inbound UDP connection 123671457 for outside:172.16.12.17/60827 (172.16.12.17/60827)(LOCAL\jpk789) to inside:10.5.141.156/53 (10.5.141.156/53)
6
Oct 30 2013
10:16:35
172.16.12.17
64207
10.5.141.155
53
Built inbound UDP connection 123671453 for outside:172.16.12.17/64207 (172.16.12.17/64207)(LOCAL\jpk789) to inside:10.5.141.155/53 (10.5.141.155/53)
6
Oct 30 2013
10:16:35
172.16.12.17
137
172.16.13.255
137
Teardown UDP connection 123671443 for outside:172.16.12.17/137(LOCAL\jpk789) to outside:172.16.13.255/137 duration 0:00:00 bytes 0
6
Oct 30 2013
10:16:35
172.16.12.17
137
172.16.13.255
137
Teardown UDP connection 123671442 for outside:172.16.12.17/137(LOCAL\jpk789) to outside:172.16.13.255/137 duration 0:00:00 bytes 0
6
Oct 30 2013
10:16:35
172.16.12.17
137
172.16.13.255
137
Teardown UDP connection 123671441 for outside:172.16.12.17/137(LOCAL\jpk789) to outside:172.16.13.255/137 duration 0:00:00 bytes 0
6
Oct 30 2013
10:16:34
IPSEC: An inbound remote access SA (SPI= 0x5650EE30) between 80.21.182.245 and 75.12.34.56 (user= jpk789) has been created.
6
Oct 30 2013
10:16:34
IPSEC: An outbound remote access SA (SPI= 0x42DBDD66) between 80.21.182.245 and 75.12.34.56 (user= jpk789) has been created.
5
Oct 30 2013
10:16:34
Local:80.21.182.245:4500 Remote:75.12.34.56:57103 Username:jpk789 SA UP. Reason: New Connection Established
4
Oct 30 2013
10:16:34
Local:80.21.182.245:4500 Remote:75.12.34.56:57103 Username:jpk789 Warning Configuration Payload request for attribute 0x7041 could not be processed. Error: Unknown/Unsupported Attribute
4
Oct 30 2013
10:16:34
Local:80.21.182.245:4500 Remote:75.12.34.56:57103 Username:jpk789 Warning Configuration Payload request for attribute 0x7040 could not be processed. Error: Unknown/Unsupported Attribute
4
Oct 30 2013
10:16:34
Local:80.21.182.245:4500 Remote:75.12.34.56:57103 Username:jpk789 Warning Configuration Payload request for attribute 0x703f could not be processed. Error: Unknown/Unsupported Attribute
4
Oct 30 2013
10:16:34
Local:80.21.182.245:4500 Remote:75.12.34.56:57103 Username:jpk789 Warning Configuration Payload request for attribute 0x703e could not be processed. Error: Unknown/Unsupported Attribute
4
Oct 30 2013
10:16:34
Local:80.21.182.245:4500 Remote:75.12.34.56:57103 Username:jpk789 Warning Configuration Payload request for attribute 0x703d could not be processed. Error: Unknown/Unsupported Attribute
4
Oct 30 2013
10:16:34
Local:80.21.182.245:4500 Remote:75.12.34.56:57103 Username:jpk789 Warning Configuration Payload request for attribute 0x703c could not be processed. Error: Unknown/Unsupported Attribute
4
Oct 30 2013
10:16:34
Local:80.21.182.245:4500 Remote:75.12.34.56:57103 Username:jpk789 Warning Configuration Payload request for attribute 0x703b could not be processed. Error: Unknown/Unsupported Attribute
6
Oct 30 2013
10:16:34
Group User IP <75.12.34.56> AnyConnect parent session started.
6
Oct 30 2013
10:16:34
DAP: User jpk789, Addr 75.12.34.56, Connection AnyConnect: The following DAP records were selected for this connection: ContosoPolicy
6
Oct 30 2013
10:16:34
AAA transaction status ACCEPT : user = jpk789
6
Oct 30 2013
10:16:34
AAA retrieved default group policy (DfltGrpPolicy) for user = jpk789
6
Oct 30 2013
10:16:34
AAA retrieved user specific group policy (useGroup1s.Grp) for user = jpk789
6
Oct 30 2013
10:16:34
AAA group policy for user jpk789 is being set to useGroup1s.Grp;
6
Oct 30 2013
10:16:34
AAA user authentication Successful : server = 192.168.7.4 : user = jpk789

WD My Passport Essential not recognized anymore

Hi, I have a WD My Passport Essential 3.0 Gen2 1TB. After 2 years of using it without any trouble, it stopped working. The blue light is on, it appears in Device Manager as USB connected, but I cannot access it - it says I need to format it, then it says "Data error (cyclic redundancy check)". I changed the drive letter - no results.Changed the USB cable - no results.Tried connecting it to another computer - no results.I tried using WD Drive Utilities, but the tests failed (quick at 90%, complete right away). I have some pictures and videos on that drive, so I don't want to format it. Is there any way I can access or recover them? Thanx in advance.

Hello,
You can try to recover the files using a data recovery software. If this does not work then you can try a data recovery company.
Data Recovery

My Passport Essential SE (USB 3.0)

Hi Community, I have 1TB My Passport Essential SE (USB 3.0) when I connect it to the PC is sound normally ,but the led is off and the HD is not detected . I tried :- 1-Changing the cable .2-Test the same cable on another HD and it work normally .3-chnaging the PC .4-changign the USB port (USB 3 and USB 2)5-connect the USB cable to the HDD while is connected to the laptop . Would you please advise . thanks .

Hello,
Seems you already tried and did the necessary troubleshooting. This means the drive is dead. If the drive is till under warranty then you can get it replaced.
How to get an RMA, (Return Merchandise Authorization) or replace a defective product under warranty

Dial-up connection disconnects when importing CDs into iTunes

When importing a CD, my dial-up Internet connection disconnects after each song has finished importing. The importing doesn't seem to be affected, but I keep having to reconnect. This is very annoying!
Has anyone else had this problem, and how can I fix it?

This is also a known phenomenon on Macs with a dial-up connection.
For Macs there is a workaround, but no solution yet.
By using an Applescript, the firewall settings will be toggled on CD insert, preventing iTunes to contact Gracenote (to get track information).
I don't know something similar for Windows.
Maybe you can write some code yourself.
The URL to block (temporary) is "http://service.gracenote.com"
You can always get the track information later by selecting all tracks of an imported CD and choosing 'Get CD Track Names' from the Advanced menu in iTunes.
M
17' iMac fp 800 MHz 768 MB RAM Mac OS X (10.4.6) Several ext. HD (backup and data)

Correct way to cleanup lccs state for Connect/Disconnect functionality

I am trying to implement connect/disconnect functionality but I got some errors - when user connects to another room after disconnect different objects(for example AudioPublisher) may end up in incorrect state. Currently I perform following sequence of actions on disconnect: call stop method on AudioPublisher, call close method on AudioPublisher, and then call close method on ConnectionSession. When I reconnect again AudioPublisher object in wrong states and throws different exceptions("Stream not found", "Stream already exists"). Can you recommend some approach to avoid these errors?
Best Regards, Aleksey

Hi Aleksey,
Seems like using multiple connectsession (connecting to different rooms) is messing your app. We handle most of the clean up in the close & stop methods for AudioPublisher. If you are still facing issues can you share your code.
Thanks
Arun

Connection closed after many connect/disconnect

Hi!
I'm connecting and disconnecting through OCCI many times in short term. After disconnect I run SQL*Loader through system command (in C). When number of that connect/disconnect pair reached about 128 I receive:
SQL*Loader-704: Internal error: ulconnect: OCIServerAttach [0]
ORA-12537: TNS:connection closedWhat should I do to fix this? Maybe some initialize parameter should be changed?

You are probably not releasing the connection handles properly.
Most likely that you are holding the 128 connection objects.
terminateConnection should be called before connecting again.
You can see how many connections are active in Oracle Server

WAN connections disconnect

Hi:
We have a connection from the outside to a system trough a FW-ASA-5520.
The thing is that the connection is disconnected while some time.
The ASA5520 disconnects any connection? Is there any timer?
Thanks. Regards.

Jimmy,
What version of firmware are you using on the rv016?
Try reflashing the Firmware/ Factory Reset/ And reload your configurations back on the device.

WD passport Essential

i have a WD external drive (My Passport Essential) which i used previously to back up my files. However a friend of mine recommended me to use CCC and i find it easier and less complication.
i am trying to remove the WD Smartware from appearing on my desktop. Tried uninstalling the smartware but eveytime i connect it to my MacBook, i could still see it there.
Any suggestions?

Look in your Accounts Login Items and see if there's any WD software being launched when you log in.
If there's nothing there stuff may be in the following locations:
~/Library/LaunchAgents (~ is your home directory)
/Library/LaunchAgents
/Library/LaunchDaemons
/Library/StartupItems
Incidentially CCC (or Super Duper) are good apps for doing backups.

Constant Connection Between Mail Server and RIM Server

Hi,
I'm a newbie in need for some advise about Blackberry Email Account
I am currently having a problem at the office. Since January 2012, our outgoing bandwidth is increasing in constant rate and it is steadily high at current time. Here are some of my findings:
there is a constant connection to port 993 (IMAPS that's being used by blackberry email account)
the constant connection is leading to RIM IP and XO Communication
the bandwidth outgoing usage is constant (at about 2.5Mbps approximately)
Our user has started setting up their office email on their personal Blackberry devices
This is causing some concern regarding our company email, does some of the email accounts got infected by virus? Please help me out with this, it might not be a normal case, but any advice to solve this problem will be highly appreciated.
Thank you,
Sandy

IMAP will be connected all the time and there has never been a BlackBerry virus.
Mail Clients will connect at all times if left on.
Do you want to block this access?
Click here to Backup the data on your BlackBerry Device! It's important, and FREE!
Click "Accept as Solution" if your problem is solved. To give thanks, click thumbs up
Click to search the Knowledge Base at BTSC and click to Read The Fabulous Manuals
BESAdmin's, please make a signature with your BES environment info.
SIM Free BlackBerry Unlocking FAQ
Follow me on Twitter @knottyrope
Want to thank me? Buy my KnottyRope App here
BES 12 and BES 5.0.4 with Exchange 2010 and SQL 2012 Hyper V

Connecting & Disconnecting Bluetooth Hangs Lumia92...

I've begun to notice that when my Lumia920 connects & disconnects multiple times with my vehicle's Bluetooth, the phone hangs & requires a restart. (It happens when I have to make multiple stops while grocery shopping)
This was not the case when I was using my simple NokiaC300. There was no problems doing the exact same tasks.
Any suggestions?

CanadaLumia920, sounds a like a bug. You should report this to the head-unit manafucturer of your car. He is able to debug this because he has your head-unit. Nokia or Microsoft might not have your head-unit. Then, your manufacturer tests your device and with his professional tools is able to debug this. Then, your manufacturer is able to determine if it is his bug, a Nokia bug or one of Microsoft (because of Windows Phone). Then, your manufacturer is able to file a qualified bug report to the one causing this. And if you have luck, it will get fixed through an software update.
The bottom line of this story: You cannot do much. Bugs happen. Rather go back to your old mobile phone. Some network operators offer to buy an additional SIM with the same number, so you can use your old and new phone in parallel.

Disable wake-up on USB connect/disconnect

Hi,
I have a USB hub with a few constantly powered slots which I use to charge and sync my iPhone. The constantly powered slot allows me to put iMac to sleep and keep the iPhone on charge. However, there is one problem - connecting or disconnecting the iPhone causes Mac to wake up. Is there a way to disable wake-up on USB connect/disconnect, but keep it on keyboard?
Thank you,
DB

You could use a special iPhone cable that lets you disconnect the sync pins for charging only.
<http://www.usbfever.com/indexeproduct_view.php?productsid=1367>
When set for charging only, it shouldn't wake the computer when you connect or disconnect the iPhone.
(Don't move the switch while the phone is connected.)
Have you checked that the phone is actually charging when the computer is sleeping? Some USB hubs may not provide full power if the computer is sleeping.

PDA continuously connecting & disconnecting

Hi All,
just tried hooking up an old Dell Axim x30i pda, and whilst it appears to be recognised ok (I haven't actually tried syncing it or anything yet), it seems to continuously connect & then be disconnected for some reason.
dmesg | tail info:
usb 2-1.3: configuration #1 chosen from 1 choice
ipaq 2-1.3:1.0: PocketPC PDA converter detected
usb 2-1.3: PocketPC PDA converter now attached to ttyUSB0
usb 2-1.3: USB disconnect, address 31
ipaq ttyUSB0: PocketPC PDA converter now disconnected from ttyUSB0
ipaq 2-1.3:1.0: device disconnected
usb 2-1.3: new full speed USB device using ehci_hcd and address 32
usb 2-1.3: configuration #1 chosen from 1 choice
ipaq 2-1.3:1.0: PocketPC PDA converter detected
usb 2-1.3: PocketPC PDA converter now attached to ttyUSB0
messages.log is filled up with repeats of the above. Could someone explain why this is happening please?

I just ran a hardware test (on ML you must hold down Option-D so it can access the hardware test bits via the 'net) and the test completed without finding any issues. I wonder if the issue has to do with switching between the integrated and discreet graphics.

Cold connection/disconnection of Firewire hard drive okay?

I have a Maxtor external hard drive that I use for backup, via a Firewire 400 port on the back of my G5. I know that I can hot-connect it to my G5 and hot disconnect it (after ejecting the disk). I back up certain files every night, appropriately connecting and disconnecting the Maxtor hard drive.
To reduce wear-and-tear on the Firewire port and the hard drive connector (because of the rate of 365 connect/disconnect cycles--or more--per year), I was wondering whether it is okay to simply keep the hard drive permanently connected to my G5 via the Firewire 400 port, so that when I want to back up, with my G5 already on, I would simply turn on the hard drive, wait for the disc to mount, do the backup, eject the disk, and then shut the disk down without disconnecting its cable from the Firewire port. Or would that damage the files on the Maxtor hard drive, or damage some software (as I understand could happen with disconnecting the external hard drive without first ejecting it)?
This is a bit of a Mac 101 question, but I've never really seen it discussed before. Thanks in advance for your feedback.

It's actually better to keep it connect all the time. Less wear and tear, like you said. Also, FireWire ports seem more prone to failure if your connect and disconnect when the power is ON. I'm sure it's a rare occurrence, but I did +burn out+ a FireWire port on my Power Mac G5 (luckily fixed while still under AppleCare), and I seem to read reports about similar failures quite a bit more often than with USB.

My Passport Essential constant connect disconnect on some windows 8.1 machines

Similar Messages

Maybe you are looking for