Re: Messenger service registration on XP SP2
- From: "Damien S" <039f4837-2145379628@xxxxxxxxxxxxxx>
- Date: Wed, 30 Aug 2006 11:38:49 -0400
The msgsvc.dll on the effected systems is version 5.1.2600.2180, so I'll try
re-registering them and restarting. The network adaptors are Intel Pro 100/VE
and are connected to a Cisco Catalyst switch. There are errors in the event
log referencing dhcp renewal being canceled by the user on startup, as well
as a trio of "link up, link down, link up" messages in the event log on
startup. The three link state events all occur within a few seconds (so the
time difference between the first and 3rd is maybe 6 seconds.)
Does that internal article offer a fix for the issue you've described?
On 8/28/2006 11:41:08 PM, wrote:
Hi Damien ,warranties,and confers no rights.
First, pleae let me know if the adapters are Bridged Network Adapters. I
ask this because I found a internal article describered that NetBIOS name
machinename<03> unregistered after reboot if a couple of Network Cards to
be Bridged Network. At the boot time, The Messenger Service enumerate
NetBIOS Interfaces and count number of Interfaces. If computer has only one
Bridged Network, it wasn't initialized at this time, Because, Messenger
Service cannot get correct lana's information. GlobalData.NumNets was 0
If it is not your case, please try:
1. Go to %systemroot%\system32 and check the msgsvc.dll.
2. Right click this dll and select properties. Check the version if it is
later than 5.1.2600.1168
3. If it is later than 5.1.2600.1168, please try to re-register it by using
: "regsvr32 msgsvc.dll" to check the results.
Hope this helps.
Best regards,
Vincent Xu
Microsoft Online Partner Support
=====================================================Get Secure! - www.microsoft.com/security
======================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others
may learn and benefit from this issue.
=====================================================This posting is provided "AS IS" with no
==================================================--------------------
<rEk0IDkyGHA.4220@xxxxxxxxxxxxxxxxxxxxx>From: "Damien S" <039f4837-2145379628@xxxxxxxxxxxxxx>
Organization: IMCPL
References: <uzam96EyGHA.4044@xxxxxxxxxxxxxxxxxxxx>
isSubject: Re: Messenger service registration on XP SP2
Lines: 70
Date: Mon, 28 Aug 2006 08:51:29 -0400
X-Newsreader: NewsMan Pro 2.6 (Freeware)
Message-ID: <u2qbmCqyGHA.3440@xxxxxxxxxxxxxxxxxxxx>
Newsgroups: microsoft.public.windowsxp.network_web
NNTP-Posting-Host: 207.250.21.100
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP06.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windowsxp.network_web:254220
X-Tomcat-NG: microsoft.public.windowsxp.network_web
Looks like I might have pasted the wrong article number. The one I was
thinking of was 306257 which describes the problem a little better. There
restartingsome vendor written software that runs on these effected PCs that requires
the Windows Messenger service in order to run properly.
On 8/27/2006 9:24:46 PM, wrote:
Hi Damien,
Would you please check the article KB878468 again? Because I see the
article applies to :
Microsoft Windows XP Service Pack 2
Microsoft Windows XP Service Pack 2
Microsoft Windows XP Tablet PC Edition 2005
Microsoft Windows XP Service Pack 2
http://support.microsoft.com/?id=878468
And in this KB artilce, it shows we workaround this problem by
accidentmessenger service.
As you described this issue happens randomly, it may be caused by
www.microsoft.com/securityand you have done the right step to restart the messenger service.
Thanks.
Best regards,
Vincent Xu
Microsoft Online Partner Support
=====================================================Get Secure! -
provided "AS IS" with no======================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others
may learn and benefit from this issue.
=====================================================This posting is
microsoft.public.windowsxp.network_web:254051warranties,and confers no rights.
==================================================--------------------
From: "Damien S" <039f4837-2145379628@xxxxxxxxxxxxxx>
Organization: IMCPL
Subject: Messenger service registration on XP SP2
Lines: 12
Date: Fri, 25 Aug 2006 10:00:07 -0400
X-Newsreader: NewsMan Pro 2.5 (Freeware)
Message-ID: <uzam96EyGHA.4044@xxxxxxxxxxxxxxxxxxxx>
Newsgroups: microsoft.public.windowsxp.network_web
NNTP-Posting-Host: 207.250.21.100
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP04.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl
butNICs,X-Tomcat-NG: microsoft.public.windowsxp.network_web
I have a pair of XP Service Pack 2 machines, with the Intel Pro 100VE
running as DHCP clients.
Sometimes when they bootup, the messenger service starts without error
messengerwon't send or recieve messages. Running nbtstat -n doesn't show the
service registrations. If the messenger service is restarted, the nbt
registrations occur correctly.
The only thing I've been able to find is kb article 878468, but it only
applies to Win2k and XP SP1.
Any ideas?
.
- Follow-Ups:
- Re: Messenger service registration on XP SP2
- From: Vincent Xu [MSFT]
- Re: Messenger service registration on XP SP2
- References:
- Messenger service registration on XP SP2
- From: Damien S
- RE: Messenger service registration on XP SP2
- From: Vincent Xu [MSFT]
- Re: Messenger service registration on XP SP2
- From: Damien S
- Re: Messenger service registration on XP SP2
- From: Vincent Xu [MSFT]
- Messenger service registration on XP SP2
- Prev by Date: Peer to Peer Network
- Next by Date: Re: Traffic evident whilst network disconnected
- Previous by thread: Re: Messenger service registration on XP SP2
- Next by thread: Re: Messenger service registration on XP SP2
- Index(es):
Relevant Pages
|
