Groove 2007 Failing to Bind to Port 1211.

[Octol]

I'm running Groove 2007 (*not* Groove Server) on Windows Server 2003
Enterprise. I continually get this message from Groove: "Failed to bind to
port 1211. Click here for more information."

When I click on the link, I get a help message that states:

"If Groove displays this alert, it means that Groove has failed to reserve a
network port for the purpose of receiving inbound messages. This might be
happening because another application has reserved the port and is blocking
Groove communications. To resolve the problem, restart your computer."

Restarting the computer does not solve the problem. The port is reserved by
svchost and it refuses to give it up. This doesn't *seem* to be causing me
any real problems, but I'd still like to correct the problem just in case.

Does anyone know how to change the default inbound port number – or know if
doing so is even a good idea? And if not, any other suggestions on how to fix
this?

Thanks.

 

[Bob Buckland ?:-\)]

Hi Octol,

You may want to use the link below to post this to the MS Office Groove discussion group as well.

===========
I'm running Groove 2007 (*not* Groove Server) on Windows Server 2003
Enterprise. I continually get this message from Groove: "Failed to bind to
port 1211. Click here for more information."

When I click on the link, I get a help message that states:

"If Groove displays this alert, it means that Groove has failed to reserve a
network port for the purpose of receiving inbound messages. This might be
happening because another application has reserved the port and is blocking
Groove communications. To resolve the problem, restart your computer."

Restarting the computer does not solve the problem. The port is reserved by
svchost and it refuses to give it up. This doesn't *seem* to be causing me
any real problems, but I'd still like to correct the problem just in case.

Does anyone know how to change the default inbound port number - or know if
doing so is even a good idea? And if not, any other suggestions on how to fix
this?

Thanks.>>
--
Please let us know if this has helped,

Bob Buckland ?
MS Office System Products MVP

LINKS
A. Specific newsgroup/discussion group mentioned in this message:
news://msnews.microsoft.com/microsoft.public.groove
or via browser:
http://microsoft.com/communities/newsgroups/en-us/?dg=microsoft.public.groove

B. MS Office Community discussion/newsgroups via Web Browser
http://microsoft.com/office/community/en-us/default.mspx
or
Microsoft hosted newsgroups via Outlook Express/newsreader
news://msnews.microsoft.com

 

[sarmakrk]

I had a similar problem. Allowing both "inbound and Outbound" on the
software firewall resolved the issue.