A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Microsoft Windows XP » General XP issues or comments
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Event ID errors 40961 and 40960 (source = LSASRV)



 
 
Thread Tools Display Modes
  #1  
Old December 10th 08, 05:26 PM posted to microsoft.public.windows.server.sbs,microsoft.public.windowsxp.general
Mike
external usenet poster
 
Posts: 9
Default Event ID errors 40961 and 40960 (source = LSASRV)

Hi All,

I'm desparate and have tried everything. I can't get a WinXP Pro SP2 (or
now SP3) to work with SBS 2003 domain controller.

I setup the PC on the main subnet and I believe it was working fine.
DNS/Reverse DNS and WINS registration working fine When it got moved to a
branch office I changed the IP (removed it's entries in DNS/WINS) so they
got re-created correctly, but I keep getting

Event ID errors 40961 and 40960 (source = LSASRV).


Here's what I've done with no success:

-Based on research installed WinXP SP3.
-Checked eventvwr and still noticed domain errors; ran windows update again.
-Tried to do a ipconfig /registerdns per recommendation of research.
-Tried to leave and re-join the domain
-Uninstalled Intel AMT because it was creating an error 2002 in the app log.
-Tried removing PC from domain, renaming PC, then rejoining domain.
-Tried running winsock fix 1.2.


Any suggestions? No other PCs at this or or other branches are having this
issue.

Thanks,
Mike

Ads
  #2  
Old December 10th 08, 05:46 PM posted to microsoft.public.windows.server.sbs,microsoft.public.windowsxp.general
Cris Hanna [SBS - MVP]
external usenet poster
 
Posts: 10
Default Event ID errors 40961 and 40960 (source = LSASRV)

Any chance this computer has McAfee installed on it?

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...69967&sr= 8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Mike" wrote in message ...
Hi All,

I'm desparate and have tried everything. I can't get a WinXP Pro SP2 (or
now SP3) to work with SBS 2003 domain controller.

I setup the PC on the main subnet and I believe it was working fine.
DNS/Reverse DNS and WINS registration working fine When it got moved to a
branch office I changed the IP (removed it's entries in DNS/WINS) so they
got re-created correctly, but I keep getting

Event ID errors 40961 and 40960 (source = LSASRV).


Here's what I've done with no success:

-Based on research installed WinXP SP3.
-Checked eventvwr and still noticed domain errors; ran windows update again.
-Tried to do a ipconfig /registerdns per recommendation of research.
-Tried to leave and re-join the domain
-Uninstalled Intel AMT because it was creating an error 2002 in the app log.
-Tried removing PC from domain, renaming PC, then rejoining domain.
-Tried running winsock fix 1.2.


Any suggestions? No other PCs at this or or other branches are having this
issue.

Thanks,
Mike

  #3  
Old December 10th 08, 06:00 PM posted to microsoft.public.windows.server.sbs,microsoft.public.windowsxp.general
Mike
external usenet poster
 
Posts: 9
Default Event ID errors 40961 and 40960 (source = LSASRV)

Nope, nor does it have Trend. All systems have Symantec Anti-virus Corp Ed ver 10.x, but this is ALL systems(incl SBS server) and this is the only one that doesn't work with the domain properly.



"Cris Hanna [SBS - MVP]" wrote in message ...
Any chance this computer has McAfee installed on it?

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...69967&sr= 8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Mike" wrote in message ...
Hi All,

I'm desparate and have tried everything. I can't get a WinXP Pro SP2 (or
now SP3) to work with SBS 2003 domain controller.

I setup the PC on the main subnet and I believe it was working fine.
DNS/Reverse DNS and WINS registration working fine When it got moved to a
branch office I changed the IP (removed it's entries in DNS/WINS) so they
got re-created correctly, but I keep getting

Event ID errors 40961 and 40960 (source = LSASRV).


Here's what I've done with no success:

-Based on research installed WinXP SP3.
-Checked eventvwr and still noticed domain errors; ran windows update again.
-Tried to do a ipconfig /registerdns per recommendation of research.
-Tried to leave and re-join the domain
-Uninstalled Intel AMT because it was creating an error 2002 in the app log.
-Tried removing PC from domain, renaming PC, then rejoining domain.
-Tried running winsock fix 1.2.


Any suggestions? No other PCs at this or or other branches are having this
issue.

Thanks,
Mike

  #4  
Old December 10th 08, 06:04 PM posted to microsoft.public.windows.server.sbs,microsoft.public.windowsxp.general
Cris Hanna [SBS - MVP]
external usenet poster
 
Posts: 10
Default Event ID errors 40961 and 40960 (source = LSASRV)

Have you already been here?
http://www.eventid.net/display.asp?e...aS rv&phase=1

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...69967&sr= 8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Mike" wrote in message ...
Nope, nor does it have Trend. All systems have Symantec Anti-virus Corp Ed ver 10.x, but this is ALL systems(incl SBS server) and this is the only one that doesn't work with the domain properly.



"Cris Hanna [SBS - MVP]" wrote in message ...
Any chance this computer has McAfee installed on it?

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...69967&sr= 8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Mike" wrote in message ...
Hi All,

I'm desparate and have tried everything. I can't get a WinXP Pro SP2 (or
now SP3) to work with SBS 2003 domain controller.

I setup the PC on the main subnet and I believe it was working fine.
DNS/Reverse DNS and WINS registration working fine When it got moved to a
branch office I changed the IP (removed it's entries in DNS/WINS) so they
got re-created correctly, but I keep getting

Event ID errors 40961 and 40960 (source = LSASRV).


Here's what I've done with no success:

-Based on research installed WinXP SP3.
-Checked eventvwr and still noticed domain errors; ran windows update again.
-Tried to do a ipconfig /registerdns per recommendation of research.
-Tried to leave and re-join the domain
-Uninstalled Intel AMT because it was creating an error 2002 in the app log.
-Tried removing PC from domain, renaming PC, then rejoining domain.
-Tried running winsock fix 1.2.


Any suggestions? No other PCs at this or or other branches are having this
issue.

Thanks,
Mike

  #5  
Old December 10th 08, 06:37 PM posted to microsoft.public.windows.server.sbs,microsoft.public.windowsxp.general
Mike
external usenet poster
 
Posts: 9
Default Event ID errors 40961 and 40960 (source = LSASRV)

Yes I have, but have not seen anything that has fixed it for me.

My Kerberos.dll file on the XP PC is 5.1.2600.5512 so this is newwer than the referenced kb/906681.

kb/259922 doesn't seem to have relevant information for the problem or a fix.

kb/938702 doesn't seem to apply because these errors are only on this PC, not on the SBS server (domain controller)

I'm also leary of kb/939820 as it's a hotfix for the server, this article doesn't reference SBS 2003, and the errors don't really match up.

Now I must say, when looking at EventID.net I'm just using their article Mxxxxxx as a Microsoft KB article as I don't subscribe to EventID. I'm assuming they are matching up with MS KB article #s.

Anything else to to try or did another suggestion seem to be more applicable? I can't be the only one having this issue.

Thanks,
Mike


"Cris Hanna [SBS - MVP]" wrote in message ...
Have you already been here?
http://www.eventid.net/display.asp?e...aS rv&phase=1

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...69967&sr= 8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Mike" wrote in message ...
Nope, nor does it have Trend. All systems have Symantec Anti-virus Corp Ed ver 10.x, but this is ALL systems(incl SBS server) and this is the only one that doesn't work with the domain properly.



"Cris Hanna [SBS - MVP]" wrote in message ...
Any chance this computer has McAfee installed on it?

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...69967&sr= 8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Mike" wrote in message ...
Hi All,

I'm desparate and have tried everything. I can't get a WinXP Pro SP2 (or
now SP3) to work with SBS 2003 domain controller.

I setup the PC on the main subnet and I believe it was working fine.
DNS/Reverse DNS and WINS registration working fine When it got moved to a
branch office I changed the IP (removed it's entries in DNS/WINS) so they
got re-created correctly, but I keep getting

Event ID errors 40961 and 40960 (source = LSASRV).


Here's what I've done with no success:

-Based on research installed WinXP SP3.
-Checked eventvwr and still noticed domain errors; ran windows update again.
-Tried to do a ipconfig /registerdns per recommendation of research.
-Tried to leave and re-join the domain
-Uninstalled Intel AMT because it was creating an error 2002 in the app log.
-Tried removing PC from domain, renaming PC, then rejoining domain.
-Tried running winsock fix 1.2.


Any suggestions? No other PCs at this or or other branches are having this
issue.

Thanks,
Mike

  #6  
Old December 10th 08, 06:45 PM posted to microsoft.public.windows.server.sbs,microsoft.public.windowsxp.general
Cris Hanna [SBS - MVP]
external usenet poster
 
Posts: 10
Default Event ID errors 40961 and 40960 (source = LSASRV)

you are correct about the ms number being the kb number

I'm afraid I'm out of ideas at this point.

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...69967&sr= 8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Mike" wrote in message ...
Yes I have, but have not seen anything that has fixed it for me.

My Kerberos.dll file on the XP PC is 5.1.2600.5512 so this is newwer than the referenced kb/906681.

kb/259922 doesn't seem to have relevant information for the problem or a fix.

kb/938702 doesn't seem to apply because these errors are only on this PC, not on the SBS server (domain controller)

I'm also leary of kb/939820 as it's a hotfix for the server, this article doesn't reference SBS 2003, and the errors don't really match up.

Now I must say, when looking at EventID.net I'm just using their article Mxxxxxx as a Microsoft KB article as I don't subscribe to EventID. I'm assuming they are matching up with MS KB article #s.

Anything else to to try or did another suggestion seem to be more applicable? I can't be the only one having this issue.

Thanks,
Mike


"Cris Hanna [SBS - MVP]" wrote in message ...
Have you already been here?
http://www.eventid.net/display.asp?e...aS rv&phase=1

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...69967&sr= 8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Mike" wrote in message ...
Nope, nor does it have Trend. All systems have Symantec Anti-virus Corp Ed ver 10.x, but this is ALL systems(incl SBS server) and this is the only one that doesn't work with the domain properly.



"Cris Hanna [SBS - MVP]" wrote in message ...
Any chance this computer has McAfee installed on it?

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...69967&sr= 8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Mike" wrote in message ...
Hi All,

I'm desparate and have tried everything. I can't get a WinXP Pro SP2 (or
now SP3) to work with SBS 2003 domain controller.

I setup the PC on the main subnet and I believe it was working fine.
DNS/Reverse DNS and WINS registration working fine When it got moved to a
branch office I changed the IP (removed it's entries in DNS/WINS) so they
got re-created correctly, but I keep getting

Event ID errors 40961 and 40960 (source = LSASRV).


Here's what I've done with no success:

-Based on research installed WinXP SP3.
-Checked eventvwr and still noticed domain errors; ran windows update again.
-Tried to do a ipconfig /registerdns per recommendation of research.
-Tried to leave and re-join the domain
-Uninstalled Intel AMT because it was creating an error 2002 in the app log.
-Tried removing PC from domain, renaming PC, then rejoining domain.
-Tried running winsock fix 1.2.


Any suggestions? No other PCs at this or or other branches are having this
issue.

Thanks,
Mike

  #7  
Old December 10th 08, 07:53 PM posted to microsoft.public.windows.server.sbs,microsoft.public.windowsxp.general
Mike
external usenet poster
 
Posts: 9
Default Event ID errors 40961 and 40960 (source = LSASRV)

Thanks, if anyone knows anything else to try please let me know.

Since the server has been running 71 days I'll try restarting that. If that doesn't work I'll probably have to get the PC shipped back for a reinstall of Windows.

Thanks,
Mike
"Cris Hanna [SBS - MVP]" wrote in message ...
you are correct about the ms number being the kb number

I'm afraid I'm out of ideas at this point.

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...69967&sr= 8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Mike" wrote in message ...
Yes I have, but have not seen anything that has fixed it for me.

My Kerberos.dll file on the XP PC is 5.1.2600.5512 so this is newwer than the referenced kb/906681.

kb/259922 doesn't seem to have relevant information for the problem or a fix.

kb/938702 doesn't seem to apply because these errors are only on this PC, not on the SBS server (domain controller)

I'm also leary of kb/939820 as it's a hotfix for the server, this article doesn't reference SBS 2003, and the errors don't really match up.

Now I must say, when looking at EventID.net I'm just using their article Mxxxxxx as a Microsoft KB article as I don't subscribe to EventID. I'm assuming they are matching up with MS KB article #s.

Anything else to to try or did another suggestion seem to be more applicable? I can't be the only one having this issue.

Thanks,
Mike


"Cris Hanna [SBS - MVP]" wrote in message ...
Have you already been here?
http://www.eventid.net/display.asp?e...aS rv&phase=1

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...69967&sr= 8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Mike" wrote in message ...
Nope, nor does it have Trend. All systems have Symantec Anti-virus Corp Ed ver 10.x, but this is ALL systems(incl SBS server) and this is the only one that doesn't work with the domain properly.



"Cris Hanna [SBS - MVP]" wrote in message ...
Any chance this computer has McAfee installed on it?

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...69967&sr= 8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Mike" wrote in message ...
Hi All,

I'm desparate and have tried everything. I can't get a WinXP Pro SP2 (or
now SP3) to work with SBS 2003 domain controller.

I setup the PC on the main subnet and I believe it was working fine.
DNS/Reverse DNS and WINS registration working fine When it got moved to a
branch office I changed the IP (removed it's entries in DNS/WINS) so they
got re-created correctly, but I keep getting

Event ID errors 40961 and 40960 (source = LSASRV).


Here's what I've done with no success:

-Based on research installed WinXP SP3.
-Checked eventvwr and still noticed domain errors; ran windows update again.
-Tried to do a ipconfig /registerdns per recommendation of research.
-Tried to leave and re-join the domain
-Uninstalled Intel AMT because it was creating an error 2002 in the app log.
-Tried removing PC from domain, renaming PC, then rejoining domain.
-Tried running winsock fix 1.2.


Any suggestions? No other PCs at this or or other branches are having this
issue.

Thanks,
Mike

  #8  
Old December 10th 08, 08:26 PM posted to microsoft.public.windows.server.sbs,microsoft.public.windowsxp.general
Cris Hanna [SBS - MVP]
external usenet poster
 
Posts: 10
Default Event ID errors 40961 and 40960 (source = LSASRV)

71 days Huh?
That would most likely mean you are behind in some patches.

Have you done reserved ports update in the registry?

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...69967&sr= 8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Mike" wrote in message ...
Thanks, if anyone knows anything else to try please let me know.

Since the server has been running 71 days I'll try restarting that. If that doesn't work I'll probably have to get the PC shipped back for a reinstall of Windows.

Thanks,
Mike
"Cris Hanna [SBS - MVP]" wrote in message ...
you are correct about the ms number being the kb number

I'm afraid I'm out of ideas at this point.

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...69967&sr= 8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Mike" wrote in message ...
Yes I have, but have not seen anything that has fixed it for me.

My Kerberos.dll file on the XP PC is 5.1.2600.5512 so this is newwer than the referenced kb/906681.

kb/259922 doesn't seem to have relevant information for the problem or a fix.

kb/938702 doesn't seem to apply because these errors are only on this PC, not on the SBS server (domain controller)

I'm also leary of kb/939820 as it's a hotfix for the server, this article doesn't reference SBS 2003, and the errors don't really match up.

Now I must say, when looking at EventID.net I'm just using their article Mxxxxxx as a Microsoft KB article as I don't subscribe to EventID. I'm assuming they are matching up with MS KB article #s.

Anything else to to try or did another suggestion seem to be more applicable? I can't be the only one having this issue.

Thanks,
Mike


"Cris Hanna [SBS - MVP]" wrote in message ...
Have you already been here?
http://www.eventid.net/display.asp?e...aS rv&phase=1

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...69967&sr= 8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Mike" wrote in message ...
Nope, nor does it have Trend. All systems have Symantec Anti-virus Corp Ed ver 10.x, but this is ALL systems(incl SBS server) and this is the only one that doesn't work with the domain properly.



"Cris Hanna [SBS - MVP]" wrote in message ...
Any chance this computer has McAfee installed on it?

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...69967&sr= 8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Mike" wrote in message ...
Hi All,

I'm desparate and have tried everything. I can't get a WinXP Pro SP2 (or
now SP3) to work with SBS 2003 domain controller.

I setup the PC on the main subnet and I believe it was working fine.
DNS/Reverse DNS and WINS registration working fine When it got moved to a
branch office I changed the IP (removed it's entries in DNS/WINS) so they
got re-created correctly, but I keep getting

Event ID errors 40961 and 40960 (source = LSASRV).


Here's what I've done with no success:

-Based on research installed WinXP SP3.
-Checked eventvwr and still noticed domain errors; ran windows update again.
-Tried to do a ipconfig /registerdns per recommendation of research.
-Tried to leave and re-join the domain
-Uninstalled Intel AMT because it was creating an error 2002 in the app log.
-Tried removing PC from domain, renaming PC, then rejoining domain.
-Tried running winsock fix 1.2.


Any suggestions? No other PCs at this or or other branches are having this
issue.

Thanks,
Mike

  #9  
Old December 11th 08, 06:35 AM posted to microsoft.public.windows.server.sbs,microsoft.public.windowsxp.general
Mike
external usenet poster
 
Posts: 9
Default Event ID errors 40961 and 40960 (source = LSASRV)

Yes, I'm behind on some updates. I plan on doing some soon. I'll start with Server 2003 SP2. I'm not familiar with the update you mentioned.

I don't understand why this would only affect 1 PC if the server is behind a little on patches.

I did reboot the server and updated the NIC driver, but it's still experiencing the issue.

Thanks,
Mike
"Cris Hanna [SBS - MVP]" wrote in message ...
71 days Huh?
That would most likely mean you are behind in some patches.

Have you done reserved ports update in the registry?

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...69967&sr= 8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Mike" wrote in message ...
Thanks, if anyone knows anything else to try please let me know.

Since the server has been running 71 days I'll try restarting that. If that doesn't work I'll probably have to get the PC shipped back for a reinstall of Windows.

Thanks,
Mike
"Cris Hanna [SBS - MVP]" wrote in message ...
you are correct about the ms number being the kb number

I'm afraid I'm out of ideas at this point.

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...69967&sr= 8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Mike" wrote in message ...
Yes I have, but have not seen anything that has fixed it for me.

My Kerberos.dll file on the XP PC is 5.1.2600.5512 so this is newwer than the referenced kb/906681.

kb/259922 doesn't seem to have relevant information for the problem or a fix.

kb/938702 doesn't seem to apply because these errors are only on this PC, not on the SBS server (domain controller)

I'm also leary of kb/939820 as it's a hotfix for the server, this article doesn't reference SBS 2003, and the errors don't really match up.

Now I must say, when looking at EventID.net I'm just using their article Mxxxxxx as a Microsoft KB article as I don't subscribe to EventID. I'm assuming they are matching up with MS KB article #s.

Anything else to to try or did another suggestion seem to be more applicable? I can't be the only one having this issue.

Thanks,
Mike


"Cris Hanna [SBS - MVP]" wrote in message ...
Have you already been here?
http://www.eventid.net/display.asp?e...aS rv&phase=1

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...69967&sr= 8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Mike" wrote in message ...
Nope, nor does it have Trend. All systems have Symantec Anti-virus Corp Ed ver 10.x, but this is ALL systems(incl SBS server) and this is the only one that doesn't work with the domain properly.



"Cris Hanna [SBS - MVP]" wrote in message ...
Any chance this computer has McAfee installed on it?

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...69967&sr= 8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Mike" wrote in message ...
Hi All,

I'm desparate and have tried everything. I can't get a WinXP Pro SP2 (or
now SP3) to work with SBS 2003 domain controller.

I setup the PC on the main subnet and I believe it was working fine.
DNS/Reverse DNS and WINS registration working fine When it got moved to a
branch office I changed the IP (removed it's entries in DNS/WINS) so they
got re-created correctly, but I keep getting

Event ID errors 40961 and 40960 (source = LSASRV).


Here's what I've done with no success:

-Based on research installed WinXP SP3.
-Checked eventvwr and still noticed domain errors; ran windows update again.
-Tried to do a ipconfig /registerdns per recommendation of research.
-Tried to leave and re-join the domain
-Uninstalled Intel AMT because it was creating an error 2002 in the app log.
-Tried removing PC from domain, renaming PC, then rejoining domain.
-Tried running winsock fix 1.2.


Any suggestions? No other PCs at this or or other branches are having this
issue.

Thanks,
Mike

  #10  
Old December 11th 08, 04:22 PM posted to microsoft.public.windows.server.sbs,microsoft.public.windowsxp.general
Mike
external usenet poster
 
Posts: 9
Default Event ID errors 40961 and 40960 (source = LSASRV)

I should also mention that the 40960 and 40961 errors in the system log occur primarly at boot. Following those erorrs I get "Userenv 1054" in the "app log" and also every time I try to run gpupdate. gpudate says successful, but the 1054 error is generated and of course policies are not working among ohter domain related functionality. I tried the nltest utility and /sc_query /sc_verify /sc_reset all complete successfully and the info reported back looks clean.

There has to be a way to fix this. It obviously knows what system the DC is and communicate with it. What command line utiilty can I use to troubleshoot further? It's at a branch but no other machines there are having issues.

Thanks,
Mike
"Mike" wrote in message ...
Yes, I'm behind on some updates. I plan on doing some soon. I'll start with Server 2003 SP2. I'm not familiar with the update you mentioned.

I don't understand why this would only affect 1 PC if the server is behind a little on patches.

I did reboot the server and updated the NIC driver, but it's still experiencing the issue.

Thanks,
Mike
"Cris Hanna [SBS - MVP]" wrote in message ...
71 days Huh?
That would most likely mean you are behind in some patches.

Have you done reserved ports update in the registry?

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...69967&sr= 8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Mike" wrote in message ...
Thanks, if anyone knows anything else to try please let me know.

Since the server has been running 71 days I'll try restarting that. If that doesn't work I'll probably have to get the PC shipped back for a reinstall of Windows.

Thanks,
Mike
"Cris Hanna [SBS - MVP]" wrote in message ...
you are correct about the ms number being the kb number

I'm afraid I'm out of ideas at this point.

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...69967&sr= 8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Mike" wrote in message ...
Yes I have, but have not seen anything that has fixed it for me.

My Kerberos.dll file on the XP PC is 5.1.2600.5512 so this is newwer than the referenced kb/906681.

kb/259922 doesn't seem to have relevant information for the problem or a fix.

kb/938702 doesn't seem to apply because these errors are only on this PC, not on the SBS server (domain controller)

I'm also leary of kb/939820 as it's a hotfix for the server, this article doesn't reference SBS 2003, and the errors don't really match up.

Now I must say, when looking at EventID.net I'm just using their article Mxxxxxx as a Microsoft KB article as I don't subscribe to EventID. I'm assuming they are matching up with MS KB article #s.

Anything else to to try or did another suggestion seem to be more applicable? I can't be the only one having this issue.

Thanks,
Mike


"Cris Hanna [SBS - MVP]" wrote in message ...
Have you already been here?
http://www.eventid.net/display.asp?e...aS rv&phase=1

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...69967&sr= 8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Mike" wrote in message ...
Nope, nor does it have Trend. All systems have Symantec Anti-virus Corp Ed ver 10.x, but this is ALL systems(incl SBS server) and this is the only one that doesn't work with the domain properly.



"Cris Hanna [SBS - MVP]" wrote in message ...
Any chance this computer has McAfee installed on it?

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...69967&sr= 8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Mike" wrote in message ...
Hi All,

I'm desparate and have tried everything. I can't get a WinXP Pro SP2 (or
now SP3) to work with SBS 2003 domain controller.

I setup the PC on the main subnet and I believe it was working fine.
DNS/Reverse DNS and WINS registration working fine When it got moved to a
branch office I changed the IP (removed it's entries in DNS/WINS) so they
got re-created correctly, but I keep getting

Event ID errors 40961 and 40960 (source = LSASRV).


Here's what I've done with no success:

-Based on research installed WinXP SP3.
-Checked eventvwr and still noticed domain errors; ran windows update again.
-Tried to do a ipconfig /registerdns per recommendation of research.
-Tried to leave and re-join the domain
-Uninstalled Intel AMT because it was creating an error 2002 in the app log.
-Tried removing PC from domain, renaming PC, then rejoining domain.
-Tried running winsock fix 1.2.


Any suggestions? No other PCs at this or or other branches are having this
issue.

Thanks,
Mike

  #11  
Old December 11th 08, 04:55 PM posted to microsoft.public.windows.server.sbs,microsoft.public.windowsxp.general
Cris Hanna [SBS - MVP]
external usenet poster
 
Posts: 10
Default Event ID errors 40961 and 40960 (source = LSASRV)

Have you run the SBS BPA?

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...69967&sr= 8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Mike" wrote in message ...
I should also mention that the 40960 and 40961 errors in the system log occur primarly at boot. Following those erorrs I get "Userenv 1054" in the "app log" and also every time I try to run gpupdate. gpudate says successful, but the 1054 error is generated and of course policies are not working among ohter domain related functionality. I tried the nltest utility and /sc_query /sc_verify /sc_reset all complete successfully and the info reported back looks clean.

There has to be a way to fix this. It obviously knows what system the DC is and communicate with it. What command line utiilty can I use to troubleshoot further? It's at a branch but no other machines there are having issues.

Thanks,
Mike
"Mike" wrote in message ...
Yes, I'm behind on some updates. I plan on doing some soon. I'll start with Server 2003 SP2. I'm not familiar with the update you mentioned.

I don't understand why this would only affect 1 PC if the server is behind a little on patches.

I did reboot the server and updated the NIC driver, but it's still experiencing the issue.

Thanks,
Mike
"Cris Hanna [SBS - MVP]" wrote in message ...
71 days Huh?
That would most likely mean you are behind in some patches.

Have you done reserved ports update in the registry?

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...69967&sr= 8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Mike" wrote in message ...
Thanks, if anyone knows anything else to try please let me know.

Since the server has been running 71 days I'll try restarting that. If that doesn't work I'll probably have to get the PC shipped back for a reinstall of Windows.

Thanks,
Mike
"Cris Hanna [SBS - MVP]" wrote in message ...
you are correct about the ms number being the kb number

I'm afraid I'm out of ideas at this point.

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...69967&sr= 8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Mike" wrote in message ...
Yes I have, but have not seen anything that has fixed it for me.

My Kerberos.dll file on the XP PC is 5.1.2600.5512 so this is newwer than the referenced kb/906681.

kb/259922 doesn't seem to have relevant information for the problem or a fix.

kb/938702 doesn't seem to apply because these errors are only on this PC, not on the SBS server (domain controller)

I'm also leary of kb/939820 as it's a hotfix for the server, this article doesn't reference SBS 2003, and the errors don't really match up.

Now I must say, when looking at EventID.net I'm just using their article Mxxxxxx as a Microsoft KB article as I don't subscribe to EventID. I'm assuming they are matching up with MS KB article #s.

Anything else to to try or did another suggestion seem to be more applicable? I can't be the only one having this issue.

Thanks,
Mike


"Cris Hanna [SBS - MVP]" wrote in message ...
Have you already been here?
http://www.eventid.net/display.asp?e...aS rv&phase=1

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...69967&sr= 8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Mike" wrote in message ...
Nope, nor does it have Trend. All systems have Symantec Anti-virus Corp Ed ver 10.x, but this is ALL systems(incl SBS server) and this is the only one that doesn't work with the domain properly.



"Cris Hanna [SBS - MVP]" wrote in message ...
Any chance this computer has McAfee installed on it?

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...69967&sr= 8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Mike" wrote in message ...
Hi All,

I'm desparate and have tried everything. I can't get a WinXP Pro SP2 (or
now SP3) to work with SBS 2003 domain controller.

I setup the PC on the main subnet and I believe it was working fine.
DNS/Reverse DNS and WINS registration working fine When it got moved to a
branch office I changed the IP (removed it's entries in DNS/WINS) so they
got re-created correctly, but I keep getting

Event ID errors 40961 and 40960 (source = LSASRV).


Here's what I've done with no success:

-Based on research installed WinXP SP3.
-Checked eventvwr and still noticed domain errors; ran windows update again.
-Tried to do a ipconfig /registerdns per recommendation of research.
-Tried to leave and re-join the domain
-Uninstalled Intel AMT because it was creating an error 2002 in the app log.
-Tried removing PC from domain, renaming PC, then rejoining domain.
-Tried running winsock fix 1.2.


Any suggestions? No other PCs at this or or other branches are having this
issue.

Thanks,
Mike

  #12  
Old December 11th 08, 09:13 PM posted to microsoft.public.windows.server.sbs,microsoft.public.windowsxp.general
Mike
external usenet poster
 
Posts: 9
Default Event ID errors 40961 and 40960 (source = LSASRV)

Hi Cris,

I have not ran SBS BPA. I figured the problem I'm experieincing is only on the 1 PC so that it's not server misconfiguration. I'm not against BPA. If I install and run during business hours should I expect any issues (need for reboot, etc)?

I just noticed the 1054 userenv error is on other branch office PCs (this and other branches). While they do not have problems like this PC nor do they have the 40960 and 40961 errors, I think there could be an issue with certain windows networking traffic being lost on the VPNs to the branch offices. We're using Fortinet and I'm looking into how to change the MTU on the VPN only. I can only ping accross the VPN with a MTU of 1418. At 1419 all ICMP is lost. Tried changing on the client only but that's not working. I suspect I'd need to change the server too and can't reboot during business hours.

Suggestions/thoughts?

Thanks,
Mike


"Cris Hanna [SBS - MVP]" wrote in message ...
Have you run the SBS BPA?

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...69967&sr= 8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Mike" wrote in message ...
I should also mention that the 40960 and 40961 errors in the system log occur primarly at boot. Following those erorrs I get "Userenv 1054" in the "app log" and also every time I try to run gpupdate. gpudate says successful, but the 1054 error is generated and of course policies are not working among ohter domain related functionality. I tried the nltest utility and /sc_query /sc_verify /sc_reset all complete successfully and the info reported back looks clean.

There has to be a way to fix this. It obviously knows what system the DC is and communicate with it. What command line utiilty can I use to troubleshoot further? It's at a branch but no other machines there are having issues.

Thanks,
Mike
"Mike" wrote in message ...
Yes, I'm behind on some updates. I plan on doing some soon. I'll start with Server 2003 SP2. I'm not familiar with the update you mentioned.

I don't understand why this would only affect 1 PC if the server is behind a little on patches.

I did reboot the server and updated the NIC driver, but it's still experiencing the issue.

Thanks,
Mike
"Cris Hanna [SBS - MVP]" wrote in message ...
71 days Huh?
That would most likely mean you are behind in some patches.

Have you done reserved ports update in the registry?

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...69967&sr= 8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Mike" wrote in message ...
Thanks, if anyone knows anything else to try please let me know.

Since the server has been running 71 days I'll try restarting that. If that doesn't work I'll probably have to get the PC shipped back for a reinstall of Windows.

Thanks,
Mike
"Cris Hanna [SBS - MVP]" wrote in message ...
you are correct about the ms number being the kb number

I'm afraid I'm out of ideas at this point.

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...69967&sr= 8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Mike" wrote in message ...
Yes I have, but have not seen anything that has fixed it for me.

My Kerberos.dll file on the XP PC is 5.1.2600.5512 so this is newwer than the referenced kb/906681.

kb/259922 doesn't seem to have relevant information for the problem or a fix.

kb/938702 doesn't seem to apply because these errors are only on this PC, not on the SBS server (domain controller)

I'm also leary of kb/939820 as it's a hotfix for the server, this article doesn't reference SBS 2003, and the errors don't really match up.

Now I must say, when looking at EventID.net I'm just using their article Mxxxxxx as a Microsoft KB article as I don't subscribe to EventID. I'm assuming they are matching up with MS KB article #s.

Anything else to to try or did another suggestion seem to be more applicable? I can't be the only one having this issue.

Thanks,
Mike


"Cris Hanna [SBS - MVP]" wrote in message ...
Have you already been here?
http://www.eventid.net/display.asp?e...aS rv&phase=1

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...69967&sr= 8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Mike" wrote in message ...
Nope, nor does it have Trend. All systems have Symantec Anti-virus Corp Ed ver 10.x, but this is ALL systems(incl SBS server) and this is the only one that doesn't work with the domain properly.



"Cris Hanna [SBS - MVP]" wrote in message ...
Any chance this computer has McAfee installed on it?

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...69967&sr= 8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Mike" wrote in message ...
Hi All,

I'm desparate and have tried everything. I can't get a WinXP Pro SP2 (or
now SP3) to work with SBS 2003 domain controller.

I setup the PC on the main subnet and I believe it was working fine.
DNS/Reverse DNS and WINS registration working fine When it got moved to a
branch office I changed the IP (removed it's entries in DNS/WINS) so they
got re-created correctly, but I keep getting

Event ID errors 40961 and 40960 (source = LSASRV).


Here's what I've done with no success:

-Based on research installed WinXP SP3.
-Checked eventvwr and still noticed domain errors; ran windows update again.
-Tried to do a ipconfig /registerdns per recommendation of research.
-Tried to leave and re-join the domain
-Uninstalled Intel AMT because it was creating an error 2002 in the app log.
-Tried removing PC from domain, renaming PC, then rejoining domain.
-Tried running winsock fix 1.2.


Any suggestions? No other PCs at this or or other branches are having this
issue.

Thanks,
Mike

  #13  
Old December 11th 08, 09:56 PM posted to microsoft.public.windows.server.sbs,microsoft.public.windowsxp.general
Cris Hanna [SBS - MVP]
external usenet poster
 
Posts: 10
Default Event ID errors 40961 and 40960 (source = LSASRV)

The BPA does not require a reboot nor will it affect performance

Unless you start fixing the things it finds.

I'd correct all of that...then retackle...

Since MTU is having some effect, assuming this is DSL?

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...69967&sr= 8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Mike" wrote in message ...
Hi Cris,

I have not ran SBS BPA. I figured the problem I'm experieincing is only on the 1 PC so that it's not server misconfiguration. I'm not against BPA. If I install and run during business hours should I expect any issues (need for reboot, etc)?

I just noticed the 1054 userenv error is on other branch office PCs (this and other branches). While they do not have problems like this PC nor do they have the 40960 and 40961 errors, I think there could be an issue with certain windows networking traffic being lost on the VPNs to the branch offices. We're using Fortinet and I'm looking into how to change the MTU on the VPN only. I can only ping accross the VPN with a MTU of 1418. At 1419 all ICMP is lost. Tried changing on the client only but that's not working. I suspect I'd need to change the server too and can't reboot during business hours.

Suggestions/thoughts?

Thanks,
Mike


"Cris Hanna [SBS - MVP]" wrote in message ...
Have you run the SBS BPA?

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...69967&sr= 8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Mike" wrote in message ...
I should also mention that the 40960 and 40961 errors in the system log occur primarly at boot. Following those erorrs I get "Userenv 1054" in the "app log" and also every time I try to run gpupdate. gpudate says successful, but the 1054 error is generated and of course policies are not working among ohter domain related functionality. I tried the nltest utility and /sc_query /sc_verify /sc_reset all complete successfully and the info reported back looks clean.

There has to be a way to fix this. It obviously knows what system the DC is and communicate with it. What command line utiilty can I use to troubleshoot further? It's at a branch but no other machines there are having issues.

Thanks,
Mike
"Mike" wrote in message ...
Yes, I'm behind on some updates. I plan on doing some soon. I'll start with Server 2003 SP2. I'm not familiar with the update you mentioned.

I don't understand why this would only affect 1 PC if the server is behind a little on patches.

I did reboot the server and updated the NIC driver, but it's still experiencing the issue.

Thanks,
Mike
"Cris Hanna [SBS - MVP]" wrote in message ...
71 days Huh?
That would most likely mean you are behind in some patches.

Have you done reserved ports update in the registry?

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...69967&sr= 8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Mike" wrote in message ...
Thanks, if anyone knows anything else to try please let me know.

Since the server has been running 71 days I'll try restarting that. If that doesn't work I'll probably have to get the PC shipped back for a reinstall of Windows.

Thanks,
Mike
"Cris Hanna [SBS - MVP]" wrote in message ...
you are correct about the ms number being the kb number

I'm afraid I'm out of ideas at this point.

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...69967&sr= 8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Mike" wrote in message ...
Yes I have, but have not seen anything that has fixed it for me.

My Kerberos.dll file on the XP PC is 5.1.2600.5512 so this is newwer than the referenced kb/906681.

kb/259922 doesn't seem to have relevant information for the problem or a fix.

kb/938702 doesn't seem to apply because these errors are only on this PC, not on the SBS server (domain controller)

I'm also leary of kb/939820 as it's a hotfix for the server, this article doesn't reference SBS 2003, and the errors don't really match up.

Now I must say, when looking at EventID.net I'm just using their article Mxxxxxx as a Microsoft KB article as I don't subscribe to EventID. I'm assuming they are matching up with MS KB article #s.

Anything else to to try or did another suggestion seem to be more applicable? I can't be the only one having this issue.

Thanks,
Mike


"Cris Hanna [SBS - MVP]" wrote in message ...
Have you already been here?
http://www.eventid.net/display.asp?e...aS rv&phase=1

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...69967&sr= 8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Mike" wrote in message ...
Nope, nor does it have Trend. All systems have Symantec Anti-virus Corp Ed ver 10.x, but this is ALL systems(incl SBS server) and this is the only one that doesn't work with the domain properly.



"Cris Hanna [SBS - MVP]" wrote in message ...
Any chance this computer has McAfee installed on it?

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...69967&sr= 8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Mike" wrote in message ...
Hi All,

I'm desparate and have tried everything. I can't get a WinXP Pro SP2 (or
now SP3) to work with SBS 2003 domain controller.

I setup the PC on the main subnet and I believe it was working fine.
DNS/Reverse DNS and WINS registration working fine When it got moved to a
branch office I changed the IP (removed it's entries in DNS/WINS) so they
got re-created correctly, but I keep getting

Event ID errors 40961 and 40960 (source = LSASRV).


Here's what I've done with no success:

-Based on research installed WinXP SP3.
-Checked eventvwr and still noticed domain errors; ran windows update again.
-Tried to do a ipconfig /registerdns per recommendation of research.
-Tried to leave and re-join the domain
-Uninstalled Intel AMT because it was creating an error 2002 in the app log.
-Tried removing PC from domain, renaming PC, then rejoining domain.
-Tried running winsock fix 1.2.


Any suggestions? No other PCs at this or or other branches are having this
issue.

Thanks,
Mike

  #14  
Old December 11th 08, 10:44 PM posted to microsoft.public.windows.server.sbs,microsoft.public.windowsxp.general
Mike
external usenet poster
 
Posts: 9
Default Event ID errors 40961 and 40960 (source = LSASRV)

Nope, these are T1s. They're dynamic T1s (xdata) and bonded (so 3 up/down). Fortinet confirmed that the ISP may be not forwarding fragmented esp packets. I'm checking with then now and I'll let you know the results of this and the BPA.

Thanks,
Mike
"Cris Hanna [SBS - MVP]" wrote in message ...
The BPA does not require a reboot nor will it affect performance

Unless you start fixing the things it finds.

I'd correct all of that...then retackle...

Since MTU is having some effect, assuming this is DSL?

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...69967&sr= 8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Mike" wrote in message ...
Hi Cris,

I have not ran SBS BPA. I figured the problem I'm experieincing is only on the 1 PC so that it's not server misconfiguration. I'm not against BPA. If I install and run during business hours should I expect any issues (need for reboot, etc)?

I just noticed the 1054 userenv error is on other branch office PCs (this and other branches). While they do not have problems like this PC nor do they have the 40960 and 40961 errors, I think there could be an issue with certain windows networking traffic being lost on the VPNs to the branch offices. We're using Fortinet and I'm looking into how to change the MTU on the VPN only. I can only ping accross the VPN with a MTU of 1418. At 1419 all ICMP is lost. Tried changing on the client only but that's not working. I suspect I'd need to change the server too and can't reboot during business hours.

Suggestions/thoughts?

Thanks,
Mike


"Cris Hanna [SBS - MVP]" wrote in message ...
Have you run the SBS BPA?

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...69967&sr= 8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Mike" wrote in message ...
I should also mention that the 40960 and 40961 errors in the system log occur primarly at boot. Following those erorrs I get "Userenv 1054" in the "app log" and also every time I try to run gpupdate. gpudate says successful, but the 1054 error is generated and of course policies are not working among ohter domain related functionality. I tried the nltest utility and /sc_query /sc_verify /sc_reset all complete successfully and the info reported back looks clean.

There has to be a way to fix this. It obviously knows what system the DC is and communicate with it. What command line utiilty can I use to troubleshoot further? It's at a branch but no other machines there are having issues.

Thanks,
Mike
"Mike" wrote in message ...
Yes, I'm behind on some updates. I plan on doing some soon. I'll start with Server 2003 SP2. I'm not familiar with the update you mentioned.

I don't understand why this would only affect 1 PC if the server is behind a little on patches.

I did reboot the server and updated the NIC driver, but it's still experiencing the issue.

Thanks,
Mike
"Cris Hanna [SBS - MVP]" wrote in message ...
71 days Huh?
That would most likely mean you are behind in some patches.

Have you done reserved ports update in the registry?

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...69967&sr= 8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Mike" wrote in message ...
Thanks, if anyone knows anything else to try please let me know.

Since the server has been running 71 days I'll try restarting that. If that doesn't work I'll probably have to get the PC shipped back for a reinstall of Windows.

Thanks,
Mike
"Cris Hanna [SBS - MVP]" wrote in message ...
you are correct about the ms number being the kb number

I'm afraid I'm out of ideas at this point.

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...69967&sr= 8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Mike" wrote in message ...
Yes I have, but have not seen anything that has fixed it for me.

My Kerberos.dll file on the XP PC is 5.1.2600.5512 so this is newwer than the referenced kb/906681.

kb/259922 doesn't seem to have relevant information for the problem or a fix.

kb/938702 doesn't seem to apply because these errors are only on this PC, not on the SBS server (domain controller)

I'm also leary of kb/939820 as it's a hotfix for the server, this article doesn't reference SBS 2003, and the errors don't really match up.

Now I must say, when looking at EventID.net I'm just using their article Mxxxxxx as a Microsoft KB article as I don't subscribe to EventID. I'm assuming they are matching up with MS KB article #s.

Anything else to to try or did another suggestion seem to be more applicable? I can't be the only one having this issue.

Thanks,
Mike


"Cris Hanna [SBS - MVP]" wrote in message ...
Have you already been here?
http://www.eventid.net/display.asp?e...aS rv&phase=1

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...69967&sr= 8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Mike" wrote in message ...
Nope, nor does it have Trend. All systems have Symantec Anti-virus Corp Ed ver 10.x, but this is ALL systems(incl SBS server) and this is the only one that doesn't work with the domain properly.



"Cris Hanna [SBS - MVP]" wrote in message ...
Any chance this computer has McAfee installed on it?

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...69967&sr= 8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Mike" wrote in message ...
Hi All,

I'm desparate and have tried everything. I can't get a WinXP Pro SP2 (or
now SP3) to work with SBS 2003 domain controller.

I setup the PC on the main subnet and I believe it was working fine.
DNS/Reverse DNS and WINS registration working fine When it got moved to a
branch office I changed the IP (removed it's entries in DNS/WINS) so they
got re-created correctly, but I keep getting

Event ID errors 40961 and 40960 (source = LSASRV).


Here's what I've done with no success:

-Based on research installed WinXP SP3.
-Checked eventvwr and still noticed domain errors; ran windows update again.
-Tried to do a ipconfig /registerdns per recommendation of research.
-Tried to leave and re-join the domain
-Uninstalled Intel AMT because it was creating an error 2002 in the app log.
-Tried removing PC from domain, renaming PC, then rejoining domain.
-Tried running winsock fix 1.2.


Any suggestions? No other PCs at this or or other branches are having this
issue.

Thanks,
Mike

 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off






All times are GMT +1. The time now is 03:30 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.