IP stack breaks after applying Security Software update 8.0.2.6 on NIS2008.5 on SP3

Norton Security | Norton Internet Security
1

Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Sed posuere consectetur est at lobortis. Vestibulum id ligula porta felis euismod semper. Donec ullamcorper nulla non metus auctor fringilla. Aenean lacinia bibendum nulla sed consectetur. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Cras mattis consectetur purus sit amet fermentum. Morbi leo risus, porta ac consectetur ac, vestibulum at eros. Sed posuere consectetur est at lobortis. Etiam porta sem malesuada magna mollis euismod. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Aenean eu leo quam. Pellentesque ornare sem lacinia quam venenatis vestibulum. Curabitur blandit tempus porttitor. Sed posuere consectetur est at lobortis.

2

I opened a ticket ([Incident:{removed}) on the problem, updated from NIS2008 to NIS2008.5, ran the registry fix (SymRegFix.exe)m but the problem persists.


Did you receive a respose from this ticket, you did'nt make that clear? And if so, did you subit these results in a reply?

Message Edited by johna on 07-05-2008 05:42 AM
 
[edit: applied same edit to quote.]
Message Edited by Allen_K on 07-05-2008 11:00 AM
2 Likes
3

I submitted all documentation and, as I posted above, the problem remains unresolved.

4

I take it you mean Symantec has not responeded to your ticket.

 

Let us know if this is the case.

Message Edited by johna on 07-05-2008 08:29 AM
Message Edited by johna on 07-05-2008 08:59 AM
Message Edited by johna on 07-05-2008 09:01 AM
5

Did you contact our Customer Support Team via email, or through Chat, or on the phone? You may wish to use the Chat feature built into Norton Internet Security to contact our support team. This may be the quickest way to resolve your issue, since you can allow the team to access your system to resolve the issue. I apologize for the delay; any additional information you have about the problem is appreciated. Thanks!

6

Symantec Customer Support has gone back and forth with me on this. The first suggestion was to download NIS2008.5 and remove the orginal install. That did not make any difference. Then I was told to run the SymFixReg tool. That eliminates a lot of erroroneous registry entries from the SP3 install, but did not make any difference in the problem. I've sent screen shots of the issue to the support person, but he doesn't seem to understand that the only error messages that I get are from the inability to access any of the network adapters when the problem happens.

 

Do you have a way from keeping the Symantec Network Driver update from installling? Anytime that 8.0.2.6 gets onto this system, it's curtains for the IP stack.

 

BTW, this system has been running without this kind of failure since July, 2004 until I install the latest LiveUpdate. I've been running SP3 since April, 2008 without any sort of issues. My suspicion is that the Symantec Network Security Miniport is not functioning correctly during initialization. The current version that works is 8.0.1.17 dated 2/4/08

 

Thanks for your reply.

Message Edited by bermanh5101 on 07-05-2008 10:05 AM
7

bermanh5101, I'm sorry to hear about your problem. I'm also a little surprised because that update should only have a few fixes for Windows XP systems. I've asked somebody more familiar with this component and update to follow-up with you so that we can figure out what's going on.

8

bermanh5101, I have a few requests from the team:

 

The resetlog.txt that you generated when using netsh to reset the ip stack when your network is in the broken state

An IPCONFIG dump when the network is in the broken state (ipconfig /all)

Winsock catalog dump when in broken state (run command: netsh winsock show catalog)

SND*.log Patch logs located in Windows\Temp

System Info export from msinfo32

System Event log export from event viewer (administrative tools)

 

You can also provide a NetDiag.log but will need to install the tools from the Windows XP install CD.  This is located under Support\Tools – install with Complete option

Then from command prompt run this command: netdiag.exe /debug /l   ß- ( this lower case L)  which will log into a file called NetDiag.log

 

9

OK, Here are the two logs that I have now:

 

RESETLOG.TXT

 
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\DefaultTtl
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\DontAddDefaultGatewayDefault
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\EnableIcmpRedirect
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\EnablePmtuBhDetect
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\EnablePmtuDiscovery
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\EnableSecurityFilters
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\SearchList
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\TcpWindowSize
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\UseDomainNameDevolution
reset   Linkage\UpperBind for PCI\VEN_168C&DEV_1014&SUBSYS_057E1014&REV_01\4&39A85202&0&10F0.  bad value was:
            REG_MULTI_SZ =
                SymIM
reset   Linkage\UpperBind for ROOT\NET\0000.  bad value was:
            REG_MULTI_SZ =
                SymIM
reset   Linkage\UpperBind for PCI\VEN_168C&DEV_1014&SUBSYS_833117AB&REV_01\4&39A85202&0&10F0.  bad value was:
            REG_MULTI_SZ =
                SymIM
reset   Linkage\UpperBind for PCI\VEN_8086&DEV_101E&SUBSYS_05491014&REV_03\4&39A85202&0&08F0.  bad value was:
            REG_MULTI_SZ =
                TVTPktFilter
reset   Linkage\UpperBind for ROOT\MS_NDISWANIP\0000.  bad value was:
            REG_MULTI_SZ =
                SymIM
<completed>
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{9BB8B03B-F66C-4FAC-8D73-56E969BE3CEE}\IpAutoconfigurationAddress
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{9BB8B03B-F66C-4FAC-8D73-56E969BE3CEE}\IpAutoconfigurationMask
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{9BB8B03B-F66C-4FAC-8D73-56E969BE3CEE}\IpAutoconfigurationSeed
reset   Linkage\UpperBind for PCI\VEN_168C&DEV_1014&SUBSYS_057E1014&REV_01\4&39A85202&0&10F0.  bad value was:
            REG_MULTI_SZ =
                SymIM
reset   Linkage\UpperBind for ROOT\NET\0000.  bad value was:
            REG_MULTI_SZ =
                TVTPktFilter
reset   Linkage\UpperBind for PCI\VEN_168C&DEV_1014&SUBSYS_833117AB&REV_01\4&39A85202&0&10F0.  bad value was:
            REG_MULTI_SZ =
                SymIM
reset   Linkage\UpperBind for PCI\VEN_8086&DEV_101E&SUBSYS_05491014&REV_03\4&39A85202&0&08F0.  bad value was:
            REG_MULTI_SZ =
                TVTPktFilter
reset   Linkage\UpperBind for ROOT\MS_NDISWANIP\0000.  bad value was:
            REG_MULTI_SZ =
                TVTPktFilter
<completed>
reset   SYSTEM\CurrentControlSet\Services\Netbt\Parameters\Interfaces\Tcpip_{9BB8B03B-F66C-4FAC-8D73-56E969BE3CEE}\NameServerList
            old REG_MULTI_SZ =
                <empty>
deleted SYSTEM\CurrentControlSet\Services\Netbt\Parameters\EnableDns
deleted SYSTEM\CurrentControlSet\Services\Netbt\Parameters\EnableLmhosts
deleted SYSTEM\CurrentControlSet\Services\Netbt\Parameters\ScopeId
reset   SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{9BB8B03B-F66C-4FAC-8D73-56E969BE3CEE}\DefaultGateway
            old REG_MULTI_SZ =
                <empty>
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{9BB8B03B-F66C-4FAC-8D73-56E969BE3CEE}\IpAutoconfigurationAddress
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{9BB8B03B-F66C-4FAC-8D73-56E969BE3CEE}\IpAutoconfigurationMask
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{9BB8B03B-F66C-4FAC-8D73-56E969BE3CEE}\IpAutoconfigurationSeed
reset   SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{9BB8B03B-F66C-4FAC-8D73-56E969BE3CEE}\NameServer
            old REG_SZ =
reset   Linkage\UpperBind for PCI\VEN_168C&DEV_1014&SUBSYS_057E1014&REV_01\4&39A85202&0&10F0.  bad value was:
            REG_MULTI_SZ =
                TVTPktFilter
reset   Linkage\UpperBind for ROOT\NET\0000.  bad value was:
            REG_MULTI_SZ =
                SymIM
reset   Linkage\UpperBind for PCI\VEN_168C&DEV_1014&SUBSYS_833117AB&REV_01\4&39A85202&0&10F0.  bad value was:
            REG_MULTI_SZ =
                SymIM
reset   Linkage\UpperBind for PCI\VEN_8086&DEV_101E&SUBSYS_05491014&REV_03\4&39A85202&0&08F0.  bad value was:
            REG_MULTI_SZ =
                SymIM
reset   Linkage\UpperBind for ROOT\MS_NDISWANIP\0000.  bad value was:
            REG_MULTI_SZ =
                SymIM
<completed>
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{60C2804C-8565-4CAC-888A-746B3539B0AB}\IpAutoconfigurationAddress
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{60C2804C-8565-4CAC-888A-746B3539B0AB}\IpAutoconfigurationMask
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{60C2804C-8565-4CAC-888A-746B3539B0AB}\IpAutoconfigurationSeed
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{9BB8B03B-F66C-4FAC-8D73-56E969BE3CEE}\IpAutoconfigurationAddress
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{9BB8B03B-F66C-4FAC-8D73-56E969BE3CEE}\IpAutoconfigurationMask
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{9BB8B03B-F66C-4FAC-8D73-56E969BE3CEE}\IpAutoconfigurationSeed
reset   Linkage\UpperBind for PCI\VEN_168C&DEV_1014&SUBSYS_057E1014&REV_01\4&39A85202&0&10F0.  bad value was:
            REG_MULTI_SZ =
                SymIM
reset   Linkage\UpperBind for ROOT\NET\0000.  bad value was:
            REG_MULTI_SZ =
                TVTPktFilter
reset   Linkage\UpperBind for PCI\VEN_168C&DEV_1014&SUBSYS_833117AB&REV_01\4&39A85202&0&10F0.  bad value was:
            REG_MULTI_SZ =
                SymIM
reset   Linkage\UpperBind for PCI\VEN_8086&DEV_101E&SUBSYS_05491014&REV_03\4&39A85202&0&08F0.  bad value was:
            REG_MULTI_SZ =
                TVTPktFilter
reset   Linkage\UpperBind for ROOT\MS_NDISWANIP\0000.  bad value was:
            REG_MULTI_SZ =
                TVTPktFilter
<completed>
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{9BB8B03B-F66C-4FAC-8D73-56E969BE3CEE}\IpAutoconfigurationAddress
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{9BB8B03B-F66C-4FAC-8D73-56E969BE3CEE}\IpAutoconfigurationMask
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{9BB8B03B-F66C-4FAC-8D73-56E969BE3CEE}\IpAutoconfigurationSeed
reset   Linkage\UpperBind for PCI\VEN_168C&DEV_1014&SUBSYS_057E1014&REV_01\4&39A85202&0&10F0.  bad value was:
            REG_MULTI_SZ =
                TVTPktFilter
reset   Linkage\UpperBind for ROOT\NET\0000.  bad value was:
            REG_MULTI_SZ =
                SymIM
reset   Linkage\UpperBind for PCI\VEN_168C&DEV_1014&SUBSYS_833117AB&REV_01\4&39A85202&0&10F0.  bad value was:
            REG_MULTI_SZ =
                SymIM
reset   Linkage\UpperBind for PCI\VEN_8086&DEV_101E&SUBSYS_05491014&REV_03\4&39A85202&0&08F0.  bad value was:
            REG_MULTI_SZ =
                SymIM
reset   Linkage\UpperBind for ROOT\MS_NDISWANIP\0000.  bad value was:
            REG_MULTI_SZ =
                SymIM
<completed>
 
 
  






[edit: inserted listbox to correct thread width.]
Message Edited by Allen_K on 07-08-2008 07:56 PM
10

SNDSetup8.0.2.6.log

 

[ 07/01/08 00:34:07] -----------------------------------------------------------------
[ 07/01/08 00:34:07] Starting setup.exe (version 8.0.2.6)...
[ 07/01/08 00:34:07] Command Line: /LiveUpdate
[ 07/01/08 00:34:07] [Checking state of system]
[ 07/01/08 00:34:07] Checking for all 32bit Products using SND:
[ 07/01/08 00:34:07] {2DA85B02-13C0-4E6D-9A76-22E6B3DD0CB2}: (Product Name:SymNet) (Version:8.0.1.18)
[ 07/01/08 00:34:07] Checking for all x64 Products using SND:
[ 07/01/08 00:34:07] ERROR_UNKNOWN_COMPONENT
[ 07/01/08 00:34:07] Checking for all SNDUpdater patches using SND:
[ 07/01/08 00:34:07] Checking for all 2005+ Consumer Products using SND:
[ 07/01/08 00:34:07] {2DA85B02-13C0-4E6D-9A76-22E6B3DD0CB2}: (Product Name:SymNet) (Version:8.0.1.18)
[ 07/01/08 00:34:07] Checking for all 64bit Consumer Products using SND:
[ 07/01/08 00:34:07] There are 1 SND clients installed. (SNDUpdaters:0 SymNet:1 SND_x64:0)
[ 07/01/08 00:34:07] [Checking version of SymNet.msi we're about to install]
[ 07/01/08 00:34:07] Read Property(SymNet.msi): ProductVersion=8.0.2.6
[ 07/01/08 00:34:07] {2DA85B02-13C0-4E6D-9A76-22E6B3DD0CB2}: (Product Name:SymNet) (Version:8.0.1.18)
[ 07/01/08 00:34:07] Out of 1 installed MSI's found, the highest version is: 8.0.1.18
[ 07/01/08 00:34:07] [Preparing to install]
[ 07/01/08 00:34:07]   Generated New ProductCode: {62FE2476-8E93-42ED-A5B7-F4D13116471A}
[ 07/01/08 00:34:07] Wrote Property(SymNet.msi): ProductCode={62FE2476-8E93-42ED-A5B7-F4D13116471A}
[ 07/01/08 00:34:07]   Updated SymNet.msi with the newly generated ProductCode.
[ 07/01/08 00:34:07] Read Property(SymNet.msi): ProductCode={62FE2476-8E93-42ED-A5B7-F4D13116471A}
[ 07/01/08 00:34:07] [Starting install]
[ 07/01/08 00:34:07] Installing: C:\DOCUME~1\ALLUSE~1\APPLIC~1\Symantec\LIVEUP~1\DOWNLO~1\Updt985\SymNet.msi
[ 07/01/08 00:34:07] Logging to: C:\WINDOWS\TEMP\SND_MSI_I_8.0.2.6.log
[ 07/01/08 00:34:07] Params: SYMSETUP=1 REBOOT=ReallySuppress ARPNOREMOVE=1 ARPSYSTEMCOMPONENT=1 MSIRESTARTMANAGERCONTROL="Disable" TSTREDIR_DONT_INSTALL_SYMEVENT=1
[ 07/01/08 00:44:03] MsiInstallProduct: A reboot is required.
[ 07/01/08 00:44:03] {2DA85B02-13C0-4E6D-9A76-22E6B3DD0CB2}: (Product Name:SymNet) (Version:8.0.1.18)
[ 07/01/08 00:44:03] {62FE2476-8E93-42ED-A5B7-F4D13116471A}: (Product Name:SymNet) (Version:8.0.2.6)
[ 07/01/08 00:44:03] SymNet.msi References went from 1 to 2.  Successful install.
[ 07/01/08 00:44:03] [Set flag for LU to prompt for reboot (if this was run through LiveUpdate)]
[ 07/01/08 00:44:03] [Updating SymSetup keys]
[ 07/01/08 00:44:03] {2DA85B02-13C0-4E6D-9A76-22E6B3DD0CB2} count transfered to {62FE2476-8E93-42ED-A5B7-F4D13116471A}
[ 07/01/08 00:44:03] Added to upgrade map {{2DA85B02-13C0-4E6D-9A76-22E6B3DD0CB2} | {62FE2476-8E93-42ED-A5B7-F4D13116471A}}
[ 07/01/08 00:44:03] [Preparing to uninstall]
[ 07/01/08 00:44:03]   Building list of ProductCodes to uninstall:
[ 07/01/08 00:44:03]     {2DA85B02-13C0-4E6D-9A76-22E6B3DD0CB2}: (Product Name:SymNet) (Version:8.0.1.18)
[ 07/01/08 00:44:03]   Found 1 ProductCodes we need to uninstall.
[ 07/01/08 00:44:03] Uninstalling MSI [1/1]: {2DA85B02-13C0-4E6D-9A76-22E6B3DD0CB2} SymNet 8.0.1.18
[ 07/01/08 00:44:03] {2DA85B02-13C0-4E6D-9A76-22E6B3DD0CB2}: (Product Name:SymNet) (Version:8.0.1.18)
[ 07/01/08 00:44:03] {62FE2476-8E93-42ED-A5B7-F4D13116471A}: (Product Name:SymNet) (Version:8.0.2.6)
[ 07/01/08 00:44:03] Uninstalling Existing SymNet.msi with ProductCode: {2DA85B02-13C0-4E6D-9A76-22E6B3DD0CB2}
[ 07/01/08 00:44:03] Logging to: C:\WINDOWS\TEMP\SND_MSI_U_8.0.2.6_8.0.1.18.log
[ 07/01/08 00:44:59] MsiConfigureProductEx: Success.
[ 07/01/08 00:44:59] {62FE2476-8E93-42ED-A5B7-F4D13116471A}: (Product Name:SymNet) (Version:8.0.2.6)
[ 07/01/08 00:44:59]  SymNet.msi References went from 2 to 1.  Successful uninstall.
[ 07/01/08 00:44:59] {62FE2476-8E93-42ED-A5B7-F4D13116471A}: (Product Name:SymNet) (Version:8.0.2.6)
[ 07/01/08 00:44:59] SymNet.msi upgrade completed successfully.
[ 07/01/08 00:44:59] [Listing SNDs Products using SNDUnin.dll]
[ 07/01/08 00:44:59] {62FE2476-8E93-42ED-A5B7-F4D13116471A}: (Product Name:SymNet) (Version:8.0.2.6)
[ 07/01/08 00:44:59] Exiting setup.exe (version 8.0.2.6) successfully.