Does OneCare use TCP port 63331?

A client's computer keeps trying to reach 192.168.1.94 on TCP port 63331. I
believe the connection attempt is coming from OneCare. 192.168.1.x was the
previous LAN network, but now the LAN is using a different IP range. I'm
thinking OneCare had been contacting this address in the past, when it was
on the LAN, but I can't see any way to tell it to stop trying. Any
suggestions?

"Paul Shapiro" <paul@xxxxxx> wrote:
Yes. That's the port that the OneCare client uses to communicate to and from the
"hub" PC in a OneCare Circle locally. The Circle is defined as all PCs using
OneCare and activated with the same LiveID (up to 3, by license). Any of those
PCs can be "promoted" to be a hub, where the status of OneCare on the monitored
PCs can be seen in OneCare.
I don't know how OneCare can be forced to stop checking for the other PC(s), but
a few things to try:
1. If the PC has Hub status, change it to not be a hub - open OneCare, click on
OneCare Circle, details for the PC name, "stop using this PC as a hub PC"
2. If it is *not* a hub, promote it to hub, same path, but select "make this PC
a hub" and sign in with the subscription LiveID
3. Uninstall OneCare and reinstall from http://onecare.live.com
-steve
--
Stephen Boots
MVP Windows Live
Windows Live OneCare Forum Moderator
sboots@xxxxxx

Thank's Stephen I was having the same problem and was curious to what that port was used for.