Groove 5038 Errors

[Cross]

Hello I was curious if anyone else are expirencing issues with Groove clients
registering with their relay server.

I am currently configuring a groove enviorment which consisit of a Manager
and Relay server in a DMZ enviroment. These two servers have full connectivty
with each other.

port 80 443 are opened to both servers

2492 is open on the relay server.

how ever any time a client take their notebook home they get an


Event Type: Warning
Event Source: Groove Relay
Event Category: None
Event ID: 5038
Date: 5/7/2007
Time: 9:57:01 PM
User: N/A
Computer: OBS-GRV-RLY
Description:
WARNING: DeviceUserRegistration: User layer message verification failed for
peer (58.106.68.122:61312) user
(grooveAccount://92zarafrj7xbzqb3z7ydutpg925e9wh88ci6ari@) on device
(dpp:///2itvxibcr8dvbyjkw7npbyiqpvbkptu9y8ii3da)

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


I also have an issue with WAN pressence.

On the internal network DPP works fine. However soon as you take a node off
the same subnet the client is deemed offline.

I know that I have 2492 TCP established from a Client over the wan to the
Relay server so I am pretty confident that Network is fine.

any ideas would be greatly apreciated

Thanks

 

[jej]

In general it looks like you have everything internal and the DMZ
configured correctly. In your case, I would look at DNS as your
external culprit. It appears that your computer name is not fully
qualified. Below is a summary of my thoughts on this problem:

Your internal clients are using WINS or DNS completion domains to get
the full name and IP address of your relay server.
Or
Your DNS for your domain is not properly configured to resolve the
exact same computer name to a different address when requested
externally. A simple test would be to find the name of your
configured relay server in your Groove Manager console. From a
command line issue the following command:
Nslookup [name of relay from GMS console]
Try this internal and externally to see if you are getting the
expected results.

 

[Cross]

Thanks for the reply.

My DNS resolution is as follows

Physical Names

XXX-GRV-RLY 10.10.1.66
XXX-GRV-MGR 10.10.167


Internal A record

grvrly.XXX.com.au 10.10.1.76 Web filters through ISA
grvmgr.XXX.com.au 10.10.1.77

External A record

grvrly.XXX.com.au 203.X.X.18
grvmgr.XXX.com.au 203.X.X.19

Does the physical name need to match the public A record ?

Thanks

 

[Cross]

All Fixed

After rebuild the entire network from scratch I ensured that all server
names matched the FQDN.

Rebuilt all my certs and she seems to work now.

Thanks

Thanks for the reply.

My DNS resolution is as follows

Physical Names

XXX-GRV-RLY 10.10.1.66
XXX-GRV-MGR 10.10.167


Internal A record

grvrly.XXX.com.au 10.10.1.76 Web filters through ISA
grvmgr.XXX.com.au 10.10.1.77

External A record

grvrly.XXX.com.au 203.X.X.18
grvmgr.XXX.com.au 203.X.X.19

Does the physical name need to match the public A record ?

Thanks

In general it looks like you have everything internal and the DMZ
configured correctly. In your case, I would look at DNS as your
external culprit. It appears that your computer name is not fully
qualified. Below is a summary of my thoughts on this problem:

Your internal clients are using WINS or DNS completion domains to get
the full name and IP address of your relay server.
Or
Your DNS for your domain is not properly configured to resolve the
exact same computer name to a different address when requested
externally. A simple test would be to find the name of your
configured relay server in your Groove Manager console. From a
command line issue the following command:
Nslookup [name of relay from GMS console]
Try this internal and externally to see if you are getting the
expected results.

 

[Ashok Hingorani]

Hi Cross
or the education of those who followed this thread what the results you now
get when you check the following parameters


TIA

bst rgds

ashok

--
groove evangelist
www.apwiz.com

All Fixed

After rebuild the entire network from scratch I ensured that all server
names matched the FQDN.

Rebuilt all my certs and she seems to work now.

Thanks

Thanks for the reply.

My DNS resolution is as follows

Physical Names

XXX-GRV-RLY 10.10.1.66
XXX-GRV-MGR 10.10.167


Internal A record

grvrly.XXX.com.au 10.10.1.76 Web filters through ISA
grvmgr.XXX.com.au 10.10.1.77

External A record

grvrly.XXX.com.au 203.X.X.18
grvmgr.XXX.com.au 203.X.X.19

Does the physical name need to match the public A record ?

Thanks

In general it looks like you have everything internal and the DMZ
configured correctly. In your case, I would look at DNS as your
external culprit. It appears that your computer name is not fully
qualified. Below is a summary of my thoughts on this problem:

Your internal clients are using WINS or DNS completion domains to get
the full name and IP address of your relay server.
Or
Your DNS for your domain is not properly configured to resolve the
exact same computer name to a different address when requested
externally. A simple test would be to find the name of your
configured relay server in your Groove Manager console. From a
command line issue the following command:
Nslookup [name of relay from GMS console]
Try this internal and externally to see if you are getting the
expected results.