HELP - It worked, now it does not!

[JohnHind]

Need help with a NetRemote - Girder interface.

I had the whole thing working, then I needed to install on a new PC built from scratch. While doing this I upgraded to the latest Girder and NetRemote, but did not change my CCF or GML files at all. I have (eventually) got everything working again, except that buttons on NetRemote no longer generate events in Girder.

Any ideas what might be wrong? The link works the other way i.e. text sent from Girder using NetRemote.SendLabel appears in NetRemote. I'm checking for events using Mark Fiechtner's Logging add-in on Girder, but nothing happens at all when I press a button on NetRemote. I've checked that both Internet Event Client and Internet Event Server add-ins are enabled. The latter has the correct password and port set, but there is nothing showing under "Open Connections".

I've also checked through the Girder log on starting NetRemote. There are no error messages and there is an NRCLIENT.REGISTER message Pld1 is the correct IP address for the NetRemote machine, but Pld2 shows 30000, presumably the port although both NetRemote and Girder Internet Event Server have the port configured to 1024.

Any ideas anyone - I'm really tearing my hair out on this!

[avid]

John,

When that happened to me, it was because of the Girder password being reset by the over-installation.

Brian

[JohnHind]

Thanks Brian, but it seems to be deeper than that. Passwords were the same, but I tried changing them anyway - now the NetRemote machine shows up in Open Connections, but still no events.

Client Server terminology always confuses me - do you know if it is Internet Event Client or Internet Event Server that is responsible for messaging from NetRemote to Girder?

[Jlee]

It's Internet Event Server.

Check your firewall settings.

[JohnHind]

The firewall possibility occured to me since the PC client works fine on the same machine as Girder, so I repeated the test with the firewall (both software and WiFi router) turned off to no effect. I've just completed a test using the PC client on a laptop over the same WiFi network and it worked, so it's just the Pocket PC client giving problems. I'll try a complete re-install.

The only port that needs to be open is the one specified on Internet Event Server settings and Girder settings on NetRemote? NRCLIENT.REGISTER Pld2 is 30000 which is NOT the port specified. Any idea what this is?

[JohnHind]

Thanks everyone.

Just to close this off, I eventually got this working by doing a HARD reset on my PPC and installing NetRemote first then my WiFi card. On the earlier installation there was a report of a dll file that could not be installed because it was "in ROM or in use" - there was nothing I could do about this because I'd already done a soft reset, so I had just clicked "ignore". After the hard reset this message did not appear and NetRemote worked immediately upon reinstalling the WiFi card without any further fiddling about.

My PPC is an iPAQ h2210 with a D-Link DCF-660W wi-fi compact flash card.

[Ben S]

Thanks for clearing that up, John. It sounded very weird.

For two way communication, NetRemote starts listening on a port (30000 by default) for Girder feedback. When NetRemote connects to Girder, it tells Girder what port it is listening on (the NRCLIENT.REGISTER you saw).

If the NRCLIENT.REGISTER was being received, then the PPC was "successfully" talking to Girder. Strange that it wouldn't send other commands.