Groove 2007 clients (Windows XP Sp2)
Groove 2007 Relay (Windows Server 2003 X64 RC2)
Groove 2007 Manager (Windows Server 2003 X64 RC2)


We have a Groove 2007 Relay and Manager set up. We are having problems
with our Groove 2007 clients going offline in relation to other clients when
they are not actually offline. And also some clients aren't receiving
workspace updates even though other workstations are.

Looking through the Connection Manager, I see that these clients are
connecting to blugro#relay.groove.microsoft.com, R0##.groove.net, and other
public relays. (where # is some number) My theory is that some of these
clients are connecting to the public relays and some are connecting to the
private relay, which is causing problems of systems not seeing each other.
I had been trying to fool the groove server by modifying the
C:\windows\system32\drivers\etc\hosts file and pointing the
groove.microsoft.com servers at our company Groove Relay. I haven't done
this for the R#.groove.net since there are too many of them!!

Could you please point us to some information somewhere about how to lock
down a groove client so that it only communicates with its local peers and
our internal Groove Relay?

Any help would be very much appreciated. We have invested a ton of money
into this setup and there is so very little public troubleshooting
information, so anything you can provide us would be invaluable!

Thank you
David

Hi David,

You may want to also post thi sin the MS Office Groove discussion group using the link below.

==========
<<"DavidK" <DavidK@discussions.microsoft.com> wrote in message newsAFBAEAF-1F52-48B5-B816-46E635A5BD67@microsoft.com...
Groove 2007 clients (Windows XP Sp2)
Groove 2007 Relay (Windows Server 2003 X64 RC2)
Groove 2007 Manager (Windows Server 2003 X64 RC2)


We have a Groove 2007 Relay and Manager set up. We are having problems
with our Groove 2007 clients going offline in relation to other clients when
they are not actually offline. And also some clients aren't receiving
workspace updates even though other workstations are.

Looking through the Connection Manager, I see that these clients are
connecting to blugro#relay.groove.microsoft.com, R0##.groove.net, and other
public relays. (where # is some number) My theory is that some of these
clients are connecting to the public relays and some are connecting to the
private relay, which is causing problems of systems not seeing each other.
I had been trying to fool the groove server by modifying the
C:\windows\system32\drivers\etc\hosts file and pointing the
groove.microsoft.com servers at our company Groove Relay. I haven't done
this for the R#.groove.net since there are too many of them!!

Could you please point us to some information somewhere about how to lock
down a groove client so that it only communicates with its local peers and
our internal Groove Relay?

Any help would be very much appreciated. We have invested a ton of money
into this setup and there is so very little public troubleshooting
information, so anything you can provide us would be invaluable!

Thank you
David<<
--
Please let us know if this has helped you,

Bob Buckland ?:-)
MS Office System Products MVP

>>*Courtesy is not expensive and can pay big dividends<<

LINKS
A. MS Office Groove news/discussion group via newsreader software
news://msnews.microsoft.com/microsoft.public.groove
or
MS Office Groove new/discussion group via browser:
http://microsoft.com/communities/new....public.groove


B. MS Office Accounting Community discussion/newsgroups via Web Browser
http://microsoft.com/office/communit...s/default.mspx
or
Microsoft hosted newsgroups via Outlook Express/newsreader
news://msnews.microsoft.com