Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Event ID:7023 IPSec Service unable to start at boot.


  • Please log in to reply

#1
out4knowledge

out4knowledge

    Member

  • Member
  • PipPip
  • 10 posts
Hello there,


I been having problems with IPSec Service not running after my system has started up. I would have never noticed it, if I did not check my Services (services.msc), and seen it set to "automatic", but it is not even running. After I found out this problem, I checked Event Viewer for more details about it. I seen that the System Log displayed an error code 7023. This problem has persisted for almost a year now, maybe even longer that that, and I was just wandering if this is the reason why I am having connection problems with my router. I listed some information about my network and system setup below.



Network & System Information:


· PC Manufacturer.........Toshiba Satellite A 105 Laptop

· OS.............................Windows Media Center Edition 2005 with SP3

· Firewall.......................COMODO Internet Security v3.12.111745.560

· Browser......................Mozilla Firefox v3.5.6

· Network Adapter..........Intel PRO/Wireless 3945ABG Network Connection

· Router........................Netgear Ruckus RangeMax Wireless Router WPN824 v2

· ISP............................Comcast Cable Service



OK, now that I listed my setup above, below I provided some information about the IPSec issue that I been having.


Error log information provided from Event Viewer:


Event ID:.........7023

Source:..........Service Control Manager

Category:........None

Type:..............Error

Description:.....The IPSEC Services service terminated with the following error: The authentication service is unknown.


Error window information provided from Services:


Could not start the IPSEC Services service on Local Computer.

Error 1747: The authentication service is unknown.



Registry key information about IPSec from Registry Editor:


Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\IPSec]
"Type"=dword:00000001
"Start"=dword:00000001
"ErrorControl"=dword:00000001
"Tag"=dword:00000004
"ImagePath"=hex(2):73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
52,00,49,00,56,00,45,00,52,00,53,00,5c,00,69,00,70,00,73,00,65,00,63,00,2e,\
00,73,00,79,00,73,00,00,00
"DisplayName"="IPSEC driver"
"Group"="PNP_TDI"
"Description"="IPSEC driver"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\IPSec\Security]
"Security"=hex:01,00,14,80,90,00,00,00,9c,00,00,00,14,00,00,00,30,00,00,00,02,\
00,1c,00,01,00,00,00,02,80,14,00,ff,01,0f,00,01,01,00,00,00,00,00,01,00,00,\
00,00,02,00,60,00,04,00,00,00,00,00,14,00,fd,01,02,00,01,01,00,00,00,00,00,\
05,12,00,00,00,00,00,18,00,ff,01,0f,00,01,02,00,00,00,00,00,05,20,00,00,00,\
20,02,00,00,00,00,14,00,8d,01,02,00,01,01,00,00,00,00,00,05,0b,00,00,00,00,\
00,18,00,fd,01,02,00,01,02,00,00,00,00,00,05,20,00,00,00,23,02,00,00,01,01,\
00,00,00,00,00,05,12,00,00,00,01,01,00,00,00,00,00,05,12,00,00,00

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\IPSec\Enum]
"0"="Root\\LEGACY_IPSEC\\0000"
"Count"=dword:00000001
"NextInstance"=dword:00000001



Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_IPSEC]
"NextInstance"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_IPSEC\0000]
"Service"="IPSec"
"Legacy"=dword:00000001
"ConfigFlags"=dword:00000000
"Class"="LegacyDriver"
"ClassGUID"="{8ECC055D-047F-11D1-A537-0000F8753ED1}"
"DeviceDesc"="IPSEC driver"
"Capabilities"=dword:00000000
"Driver"="{8ECC055D-047F-11D1-A537-0000F8753ED1}\\0013"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_IPSEC\0000\LogConf]

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_IPSEC\0000\Control]
"ActiveService"="IPSec"




I also added some registry information for Policy Agent, which is part of IPSec. I feel like this can help out the situation with my IPSec issue a bit more, hopefully leading to a solution. I provided the registry information below.


Registry key information about Policy Agent from Registry Editor:


Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\PolicyAgent]
"Type"=dword:00000020
"Start"=dword:00000002
"ErrorControl"=dword:00000001
"ImagePath"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,\
74,00,25,00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,6c,\
00,73,00,61,00,73,00,73,00,2e,00,65,00,78,00,65,00,00,00
"DisplayName"="IPSEC Services"
"DependOnService"=hex(7):52,00,50,00,43,00,53,00,53,00,00,00,54,00,63,00,70,00,\
69,00,70,00,00,00,49,00,50,00,53,00,65,00,63,00,00,00,00,00
"DependOnGroup"=hex(7):00,00
"ObjectName"="LocalSystem"
"Description"="Manages IP security policy and starts the ISAKMP/Oakley (IKE) and the IP security driver."
"PolstoreDllRegisterVersion"=dword:00000002

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\PolicyAgent\Security]
"Security"=hex:01,00,14,80,90,00,00,00,9c,00,00,00,14,00,00,00,30,00,00,00,02,\
00,1c,00,01,00,00,00,02,80,14,00,ff,01,0f,00,01,01,00,00,00,00,00,01,00,00,\
00,00,02,00,60,00,04,00,00,00,00,00,14,00,8d,00,02,00,01,01,00,00,00,00,00,\
05,0b,00,00,00,00,00,18,00,9d,01,02,00,01,02,00,00,00,00,00,05,20,00,00,00,\
23,02,00,00,00,00,18,00,ff,01,0f,00,01,02,00,00,00,00,00,05,20,00,00,00,20,\
02,00,00,00,00,14,00,fd,01,02,00,01,01,00,00,00,00,00,05,12,00,00,00,01,01,\
00,00,00,00,00,05,12,00,00,00,01,01,00,00,00,00,00,05,12,00,00,00

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\PolicyAgent\Enum]
"0"="Root\\LEGACY_POLICYAGENT\\0000"
"Count"=dword:00000001
"NextInstance"=dword:00000001



Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_POLICYAGENT]
"NextInstance"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_POLICYAGENT\0000]
"Service"="PolicyAgent"
"Legacy"=dword:00000001
"ConfigFlags"=dword:00000000
"Class"="LegacyDriver"
"ClassGUID"="{8ECC055D-047F-11D1-A537-0000F8753ED1}"
"DeviceDesc"="IPSEC Services"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_POLICYAGENT\0000\Control]
"ActiveService"="PolicyAgent"




I also have been searching some forums with the similar issue I been having, and found a few that look pretty promising. Any links that was remotely close to my problem, I listed them one by one below, with a brief description of the information found on that page.



1. The first link that caught my eye, had a real similar problem that I have. The person had problems staying connected after a period of time, which is the same issue I am having too. The person has the same error code 7023, and also has DHCP warnings which I am experiencing. They also talked about how the IPSec service affects some people that depend on it to run, with certain ISP’s. I am not even sure if my ISP depends on this service or not, so if anyone can shed some light on this, I would be truly grateful for the help. You can click here to see more of the post on Wilder’s Security forums, and if you can let me know what you think, please do.



2. Next link I found related to my issue had the same error code I had, but was mixed in with other issues that the person was having. After I read in between the lines, I found out that a user suggested that it could be Cisco Systems, Inc. software that can be affecting IPSec from not starting. Yet again, I am not even sure about this, but I did find some registry keys for Cisco when doing a search on Registry Editor. Down below, I even added all the registry information I can find for the Cisco software on my computer.


Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MMC\SnapIns\{DEA8AFA0-CC85-11d0-9CE2-0080C7221EBD}]
"NameString"="IP Security Policy Management"
"NameStringIndirect"="@C:\\WINDOWS\\system32\\ipsecsnp.dll,-2"
"NodeType"="{36703241-D16C-11d0-9CE4-0080C7221EBD}"
"Provider"="Cisco Systems, Inc."
"Version"="1.0"
"About"="{DEA8AFA2-CC85-11d0-9CE2-0080C7221EBD}"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MMC\SnapIns\{DEA8AFA0-CC85-11d0-9CE2-0080C7221EBD}\Extension]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MMC\SnapIns\{DEA8AFA0-CC85-11d0-9CE2-0080C7221EBD}\StandAlone]



Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\TOSHIBA\ConfigFree]
"CurrentVersion"="5.90.05"
"Version"="5.90.05"
"InstPath"="C:\\Program Files\\TOSHIBA\\ConfigFree"
"DisplayName"="TOSHIBA ConfigFree"
"AtherosRFCheckVersion"="2.3"
"DelHWIDMenu0"="ms_l2tpminiport"
"DelHWIDMenu1"="ms_ndiswanip"
"DelHWIDMenu2"="ms_ndiswanipx"
"DelHWIDMenu3"="ms_pptpminiport"
"DelHWIDMenu4"="MS_IrdaMiniport"
"DelHWIDMenu5"="MS_IrModemMiniport"
"DelHWIDMenu6"="SW\\{eeab7790-c514-11d1-b42b-00805fc1270e}"
"DelHWIDMenu7"="ms_ptiminiport"
"DelHWIDMenu8"="MS_PPPOEMINIPORT"
"DelHWIDMenu9"="MS_PSCHEDMP"
"DelHWIDMenu10"="V1394\\NIC1394"
"DelHWIDMenu11"="MS_NDISWANNBFOUT"
"DelHWIDMenu12"="MS_NDISWANNBFIN"
"DelHWIDMenu13"="BLUETOOTH"
"DelHWIDMenu14"="AOL_WANDRV"
"DelHWIDMenu15"="ms_bridgemp"
"DelHWIDMenu16"="pcmcia\\eicon_diehl-diva_pro-2610"
"DelHWIDMenu17"="NTSPPPOE"
"DelHWIDMenu18"="CS_VirtA"
"WiredDevice0"="PCI\\VEN_8086&DEV_1059&SUBSYS_00011179"
"WiredDevice1"="PCI\\VEN_8086&DEV_2449&SUBSYS_30138086"
"WiredDevice2"="PCI\\VEN_8086&DEV_2449&SUBSYS_FF011179"
"WiredDevice3"="PCI\\VEN_8086&DEV_1229&SUBSYS_24118086"
"WiredDevice4"="PCI\\VEN_8086&DEV_1229&SUBSYS_00031179"
"WiredDevice5"="PCI\\VEN_8086&DEV_1229&SUBSYS_00011179"
"WiredDevice6"="PCI\\VEN_8086&DEV_1031&SUBSYS_00011179"
"WiredDevice7"="PCI\\VEN_10B7&DEV_9200&SUBSYS_00011179"
"WiredDevice8"="PCI\\VEN_10EC&DEV_8139&SUBSYS_FF001179"
"WiredDevice9"="PCI\\VEN_10EC&DEV_8139&SUBSYS_00011179"
"WiredDevice10"="PCI\\VEN_8086&DEV_1016&SUBSYS_00011179"
"WiredDevice11"="PCI\\VEN_8086&DEV_103D&SUBSYS_00011179"
"WiredDevice12"="PCI\\VEN_8086&DEV_103D&SUBSYS_FF101179"
"WiredDevice13"="PCI\\VEN_10EC&DEV_8139&SUBSYS_00021179"
"WirelessDevice0"="PCMCIA\\TOSHIBA-Wireless_LAN_Card-615B"
"WirelessDevice1"="PCMCIA\\TOSHIBA-WIRELESS_LAN_CARD-E5D7"
"WirelessDevice2"="PCI\\VEN_14B9&DEV_5000&SUBSYS_500014B9"
"WirelessDevice3"="PCI\\VEN_14B9&DEV_A504&SUBSYS_500014B9"
"WirelessDevice4"="PCMCIA\\Lucent_Technologies-WaveLAN/IEEE-C908"
"WirelessDevice5"="PCI\\VEN_168C&DEV_0012&SUBSYS_7005144F"
"WirelessDevice6"="PCI\\VEN_8086&DEV_1043&SUBSYS_25808086"
"WirelessDevice7"="PCI\\VEN_8086&DEV_1043&SUBSYS_25818086"
"WirelessDevice8"="PCI\\VEN_8086&DEV_1043&SUBSYS_25828086"
"WirelessDevice9"="PCMCIA\\Cisco_Systems-340_Series_Wireless_LAN_Adapter-5FE9"
"WirelessDevice10"="PCI\\VEN_8086&DEV_1043&SUBSYS_25838086"
"WirelessDevice11"="PCI\\VEN_168C&DEV_0013&SUBSYS_7057144F"
"WirelessDevice12"="PCI\\VEN_168C&DEV_0013&SUBSYS_7058144F"
"WirelessDevice13"="PCI\\VEN_8086&DEV_4220&SUBSYS_27418086"
"WirelessDevice14"="PCI\\VEN_8086&DEV_4220&SUBSYS_27428086"
"WirelessDevice15"="PCI\\VEN_168C&DEV_0013&SUBSYS_7064144F"
"WirelessDevice16"="PCI\\VEN_168C&DEV_0013&SUBSYS_7065144F"
"WirelessDevice17"="PCI\\VEN_8086&DEV_4223&SUBSYS_10408086"
"WirelessDevice18"="PCI\\VEN_8086&DEV_4223&SUBSYS_10418086"
"WirelessDevice19"="PCI\\VEN_8086&DEV_4223&SUBSYS_10428086"
"WirelessDevice20"="PCI\\VEN_8086&DEV_4223&SUBSYS_10438086"
"ORI_DevID0"="PCMCIA\\TOSHIBA-WIRELESS_LAN_CARD-E5D7"
"TI_CardBusDevice"="PCI\\VEN_104C&DEV_AC50&SUBSYS_AB0112A3&REV_01"
"InternalDevice0"="PCMCIA\\TOSHIBA-WIRELESS_LAN_CARD-E5D7"
"InternalDevice1"="PCI\\VEN_14B9&DEV_5000&SUBSYS_500014B9"
"InternalDevice2"="PCI\\VEN_14B9&DEV_A504&SUBSYS_500014B9"
"InternalDevice3"="PCI\\VEN_168C&DEV_0012&SUBSYS_7005144F"
"InternalDevice4"="PCI\\VEN_8086&DEV_1043&SUBSYS_25808086"
"InternalDevice5"="PCI\\VEN_8086&DEV_1043&SUBSYS_25818086"
"InternalDevice6"="PCI\\VEN_8086&DEV_1043&SUBSYS_25828086"
"InternalDevice7"="PCI\\VEN_8086&DEV_1043&SUBSYS_25838086"
"InternalDevice8"="PCI\\VEN_168C&DEV_0013&SUBSYS_7057144F"
"InternalDevice9"="PCI\\VEN_168C&DEV_0013&SUBSYS_7058144F"
"InternalDevice10"="PCI\\VEN_8086&DEV_4220&SUBSYS_27418086"
"InternalDevice11"="PCI\\VEN_8086&DEV_4220&SUBSYS_27428086"
"InternalDevice12"="PCI\\VEN_168C&DEV_0013&SUBSYS_7064144F"
"InternalDevice13"="PCI\\VEN_168C&DEV_0013&SUBSYS_7065144F"
"InternalDevice14"="PCI\\VEN_8086&DEV_4223&SUBSYS_10408086"
"InternalDevice15"="PCI\\VEN_8086&DEV_4223&SUBSYS_10418086"
"InternalDevice16"="PCI\\VEN_8086&DEV_4223&SUBSYS_10428086"
"InternalDevice17"="PCI\\VEN_8086&DEV_4223&SUBSYS_10438086"
"AutoFlag_WLAN"=dword:00000002
"AutoFlag_LAN"=dword:00000000
"Filter"=dword:00000007
"HideDiffDevDlg"=dword:00000000
"Wait"=dword:000007d0
"WaitRunApp"=dword:00001388
"MaxPFNumber"=dword:0000001e
"NCF_FLAG"=dword:00000008
"ShowMenu"=dword:00003faf
"DispOverview"=dword:00000000
"QC_Projector"=dword:00000001
"UseSound"=dword:00000001
"UseAsWarning"=dword:00000001
"NotUseSplash"=dword:00000000
"TosAPOption"=dword:00000000
"UseAdapterName"=dword:00000001
"MiniMemory"=dword:00000001
"EnableAllUser"=dword:00000000
"EnableNN"=dword:00000000
"ECKBCCheck"=dword:00000000
"EnableTosNetDev"=dword:00000001
"QCHideOption"=dword:00000000
"QCSearch_RD"=dword:00000000
"QCSearch_TQ"=dword:00000000
"QCSearch_WTT"=dword:00000000
"QCShowWarningFlag_NotDPJ"=dword:00000001
"ShowQconnect"=dword:00000000
"EnableWAN"=dword:00000001
"EnableSUMMIT"=dword:00000001
"EnableAerial"=dword:00000001
"EnableWiFi"=dword:00000001
"EnableBluetooth"=dword:00000001
"EnableDoctor"=dword:00000001
"EnableDevices"=dword:00000001
"EnableProfile"=dword:00000001
"EnableQConnect"=dword:00000001
"FinishSound"="C:\\Program Files\\TOSHIBA\\ConfigFree\\CFFINISH.wav"
"FoundSound"="C:\\Program Files\\TOSHIBA\\ConfigFree\\CFFOUND.wav"
"SolvedSound"="C:\\Program Files\\TOSHIBA\\ConfigFree\\CFSOLVE.wav"
"LastUpdateDate"="2-15-2006/08:36:23"
"InternalDevice18"="PCI\\VEN_168C&DEV_0013&SUBSYS_7084144F"
"InternalDevice19"="PCI\\VEN_17FE&DEV_2220&SUBSYS_03101468"
"InternalDevice20"="PCI\\VEN_168C&DEV_0013&SUBSYS_7088144F"
"InternalDevice21"="PCI\\VEN_168C&DEV_001B&SUBSYS_7092144F"
"InternalDevice22"="PCI\\VEN_168C&DEV_001A&SUBSYS_7094144F"
"InternalDevice23"="PCI\\VEN_8086&DEV_4222&SUBSYS_10408086"
"InternalDevice24"="PCI\\VEN_8086&DEV_4222&SUBSYS_10418086"
"InternalDevice25"="PCI\\VEN_8086&DEV_4222&SUBSYS_10428086"
"InternalDevice26"="PCI\\VEN_8086&DEV_4222&SUBSYS_10438086"
"InternalDevice27"="PCI\\VEN_8086&DEV_4222&SUBSYS_10058086"
"InternalDevice28"="PCI\\VEN_168C&DEV_001C&SUBSYS_7096144F"
"InternalDevice29"="PCI\\VEN_168C&DEV_001C&SUBSYS_7106144F"
"InstCheck"="Satellite A105"
"UseTWLMProtocol"=dword:00000001
"WiredDevice14"="PCI\\VEN_8086&DEV_109A&SUBSYS_00008086&REV_00\\4&192AC53F&0&00E0"
"WiredDevice15"="PCI\\VEN_8086&DEV_1092&SUBSYS_FF101179&REV_02\\4&6B16D5B&0&40F0"
"InternalDevice30"="PCI\\VEN_8086&DEV_4222&SUBSYS_10448086"
"WirelessDevice21"="PCI\\VEN_8086&DEV_4222&SUBSYS_10408086&REV_02\\4&2803E7C1&0&00E2"
"UseVenAPI"=dword:00000000
"DunLaunchDefault"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\TOSHIBA\ConfigFree\5.90.05]

[HKEY_LOCAL_MACHINE\SOFTWARE\TOSHIBA\ConfigFree\Aerial2.0]
"auPictureGuide"="glaunch.exe .\\A5504T.chm::/01_image_PHONE.htm"
"auAddressGuide"="glaunch.exe .\\A5504T.chm::/02_address_PHONE.htm"
"auDialupGuide"="glaunch.exe .\\A5504T.chm::/03_dialup_PHONE.htm"
"auWin_Guide1"="glaunch.exe .\\W21T.chm::/01_image_PHONE.htm"
"auWin_Guide2"="glaunch.exe .\\W21T.chm::/02_address_task_schedule_PHONE.htm"
"auWin_Guide3"="glaunch.exe .\\W21T.chm::/03_dialup_PHONE.htm"
"VodafoneV902T_Guide1"=""
"VodafoneV902T_Guide2"="glaunch.exe .\\PHONE_help.chm::/01_FTP_PHONE.htm"
"VodafoneV902T_Guide3"="glaunch.exe .\\PHONE_help.chm::/02_dialup_PHONE.htm"
"VodafoneTS921_Guide1"=""
"VodafoneTS921_Guide2"="glaunch.exe .\\PHONE_help.chm::/01_FTP_PHONE.htm"
"VodafoneTS921_Guide3"="glaunch.exe .\\PHONE_help.chm::/02_dialup_PHONE.htm"

[HKEY_LOCAL_MACHINE\SOFTWARE\TOSHIBA\ConfigFree\AutoSwitchESSID]

[HKEY_LOCAL_MACHINE\SOFTWARE\TOSHIBA\ConfigFree\CFMain]
"PingOption"=dword:00000000
"CFPriority"=dword:00000003
"DBVersion"="3.00.02"

[HKEY_LOCAL_MACHINE\SOFTWARE\TOSHIBA\ConfigFree\CFMain\Database]

[HKEY_LOCAL_MACHINE\SOFTWARE\TOSHIBA\ConfigFree\CFMain\Database\Log]
"TotalNum"=dword:000000a6
"Attrib=4010"=dword:000000a6
"LastSelect"=hex:02,00,00,00,00,00,00,00,10,40,00,00,10,40,00,00,00,00,00,00,\
00,00,00,00,44,45,0a,00,7c,44,0a,00,00,00,00,00,7c,44,0a,00,07,37,e8,77,58,\
00,00,00,dc,82,e7,77,b4,e2,16,00,00,40,16,00,91,c6,e7,77,48,41,16,00,c8,be,\
16,00,00,00,00,00,69,6b,92,77,00,00,00,00,00,00,00,00,a0,44,0a,00,ea,c5,e7,\
77,7c,bf,16,00,00,40,16,00,bc,44,0a,00,bc,c5,e7,77,00,40,16,00,44,45,0a,00,\
00,40,16,00,01,00,00,00,c8,be,16,00,c8,44,0a,00,71,c5,e7,77,44,45,0a,00,45,\
09,91,7c,4e,09,91,7c,3c,48,0a,00,24,00,02,00,28,46,0a,00,af,a5,91,7c,3c,45,\
0a,00,00,e0,fd,7f,05,10,90,7c,d0,44,0a,00,00,00,00,00,a0,45,0a,00,18,ee,90,\
7c,70,09,91,7c,c0,e4,97,7c,6f,3e,91,7c,62,3e,91,7c,08,02,00,00,e0,48,0a,00,\
b8,48,0a,00,54,00,00,00,10,00,00,00,10,da,16,00,c0,00,00,00,0d,00,00,00,32,\
46,0a,00,c0,6a,92,77,2a,00,00,00,06,00,00,00,54,00,56,00,00,dc,fd,7f,00,00,\
00,00,84,da,16,00,00,dc,fd,7f,08,00,00,00,54,00,08,02,45,00,00,00

[HKEY_LOCAL_MACHINE\SOFTWARE\TOSHIBA\ConfigFree\NdsBrowser]
"IconSize"=dword:00000020

[HKEY_LOCAL_MACHINE\SOFTWARE\TOSHIBA\ConfigFree\NdsTray]
"DeleteBalloonInterval"=dword:00001388
"ShowIpBalloon"=dword:00000001
"UseTraMeter"=dword:00000001
"ResumeTime"=dword:00003a98
"QCMutex"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\TOSHIBA\ConfigFree\Profiles]




As you can see above, Cisco software is either part of, or controlled by the ConfigFree software that was pre-installed on my Toshiba laptop. I use none of the software that is provided by Toshiba, and I really care less about it. If anyone knows if this is the reason why my IPSec service is not starting up on boot, and if so, are these keys safe to be removed. You can click here to better view the post for yourself that I found on The Elder Geek forums. Please let me know what you think about this situation.



3. Another link I found was on Microsoft Support page, which you can click here to view. It explains that you can encounter a connection time out when client computers that have Windows XP/Server 2003 try to connect to a server on a wireless network that uses IPSec NAT-T. What I found interesting about this page was that I am also on a wireless network, using an Intel network adapter, and the issue is based around IPSec. This article is a bit outdated (August 29, 2007), which makes me believe the hotfix offered might not patch the problem. I also want to know if anyone had any suggestions on the hotfix available. Please feel free to comment about it.



If anyone ran into this type of situation, or has any idea of how I can fix this, please reply back. If you need me to gather more information to help better troubleshoot this issue, I am willing to do everything I can to provide it. As of now, it is not causing no problems connecting, but not sure if is a security vulnerability issue, because IPSec service is not running. If you can help out in any way about this issue, please do.



Thanks,


- out4knowledge -
  • 0

Advertisements


#2
The Skeptic

The Skeptic

    Trusted Tech

  • Technician
  • 4,075 posts
Did you see this one?
  • 0

#3
out4knowledge

out4knowledge

    Member

  • Topic Starter
  • Member
  • PipPip
  • 10 posts
Thanks a lot for the link, and I will try it out as soon as possible. I will post back the results when I am able use the information provided by the link you gave me. I have already uninstalled ConfigFree software, but still the issue persists. I will see if this link can help me out, and will reply back soon.


Thanks for the help,


- out4knowledge -
  • 0

#4
xgt

xgt

    New Member

  • Member
  • Pip
  • 1 posts
maybe you can try ,1. type in command prompt :>netsh winsock reset
and reboot!
2. Reinstall >Client for Microsoft Networks
and reboot!

Edited by xgt, 12 January 2010 - 06:45 AM.

  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP