Girder 5 Beat and NR2 limits?

[Mortie]

Hi,
Is there a limitation as to how many NS clients than can connect to a trial version of Girder 5 at the same time?

It seems that I can connect two clients, but the thisd will not coonect, well it gets authenticated but no data gets back to NR.
I have to restart Girder. Is this the case?

//Morten

[Rob H]

The limit is probably in the license of NR2 - if you have a license for NR Whole Home then you should be able to connect as many NR clients as you like. Help|About should tell you your license type.

[Mortie]

I have a whole home licens for NR2.

It's wird, I've done setup and testing from one computer for the past few days, now I've installed on a new computer with a fresh installation of win xp sp2. And it is acting wierd towards girder 5. It does not coonect, then I restart girder and I get a connection. After a restart of NR I get no connection again. I've got MediaBridge running on the same computer as Girder and NR2 connects to it everytime.

This is the girder log when connection the NR client:
Time Date Source Details Payloads
22:22:34:195 4/9/2007 NetRemote No Client at 192.168.1.109
22:22:34:179 4/9/2007 Communication Server DM.DeviceUpdateDone 2336 192.168.1.109 6
22:22:33:695 4/9/2007 NetRemote Synchronising client 192.168.1.1 {07595658-e995-405b-a144-f68c98c2abcd}
22:22:33:679 4/9/2007 NetRemote Connected
22:22:33:648 4/9/2007 NetRemote Starting feedback thread for 192.168.1.1
22:22:33:632 4/9/2007 NetRemote Registering NR client
22:22:33:616 4/9/2007 NetRemote Adding client 192.168.1.1
22:22:33:601 4/9/2007 NetRemote Connection from 192.168.1.1:1410
22:22:33:570 4/9/2007 Communication Server New Client Connection 192.168.1.1 1410
22:22:33:585 4/9/2007 Communication Server Connection Authenticated 192.168.1.1 NetRemote
22:22:32:444 4/9/2007 Communication Server: Servers Server (GIRDER): seer, @ 192.168.1.3:20005
22:22:32:444 4/9/2007 Communication Server: Servers Server (MediaBridge): seer, @ 192.168.1.3:20003
22:22:32:444 4/9/2007 Communication Server Existing Client GIRDER seer 192.168.1.3 20005
22:22:32:444 4/9/2007 Communication Server Existing Client MediaBridge seer 192.168.1.3 20003




The last log entry, no client at... is ofcourse strange...

Any ideas?

Regards,
Morten

[Mortie]

After a little more research;
If I restert NR2 I loose connection to Girder5.
If I however reset the Lua scripting eninge and then start NR2, then I get a connection. This behavior I can recreate everytime.

But the wierd part is that it is nor conistent from every computer.
I have another computer that I can restart NR as much as I want with no problem, then one differens is that that computer is running Vista.

//Morten

[Rob H]

Can you take a look at the NetRemote settings in Girder when this happens?

File|Settings|Automation|NetRemote

I'm interested in the list of known clients, so a screenshot of that would be helpful.

[Mortie]

I've attached three prictures, one where the client is connected for the first time, and working, then a picture when NR is closed down. -And finally a third where NR is started again, but this time it's not working. From what I can see everything seems fine, but NR is not working.

Now, another observation:
If the client that runs NR goes into sleep mode, with NR running it will establish a connection without any problem when it gets up and running again.

Edit: I think I can narrow it down some more, it might be related to the device manager. Neither the AV Reciver nor the weather pages work, but the PC Control works just fine.

Regards,
Morten

[Mortie]

This is what happens when I restart NR from the PC that work:
Registering NR client from 192.168.1.104:59302
LOG: Device Manager : 4 - Connection manager: Got a DM.Query from NetRemote client at 192.168.1.104

Now this is whats get logged when restarting NR on the other computer:
Registering NR client from 192.168.1.109:2117

No DM.Query, o it makes sense why it does not work. But why does it happen? No idea :-)

[Rob H]

A couple of things - make sure that the real Girder plugin instance isn't -1. It should be something like -2101

Also, try to use names rather than IP addresses.

You may want to try deleting the Girder plugin instance and letting autodiscovery find it again.

[Mortie]

That's it!

The girder plugin instance was -1! Don't know why or why that is a problem, since it was autodiscorverd.
Anyway, I deletet the mapping and recreated it, then it got an id of 2001, and all is well :-)

Thank you for helping me out!

[Rob H]

Great, glad it's working now