Net Remote so unreliable- can't use

[michaeljc]

I had installed Net Remote on my iPqa rx1955. I love the program when it works. I am having a couple of recurring problems though:

1) The connectiviity seems to drop. This is even when the device doesn't go into sleep mode and I have a good connection (I verified it using IE). Often, I have to restart Net Remote or reboot the device

2) Sometimes when rebooting the PPC, it will completey freeze and I will have to do a complete hard reset, losing all my software. This si obviously time consuming.

3) Sometimes it seemed like 1 had 1 way connectivity. I could press the pause or next song button and it would work, but the display would not update.

I thought originally that there was a problem with the PPC. Note tha tI have no other software isntalled on the PPC other than Net Remote. After giving up, I started to test the PPC without the NetRemote software. I would go into IE and check connectivity, leave it a few mintues and try it again. I never had a problem with connectivity or freezing. This led me to believe it was Net Remote casuing the problem. Any ideas on what could be going on? I would like to continue using NetRemote, but it isn't worth the effort with all these problems.

[Ben S]

Hi Michael -
Regarding # 2 - You can also do a soft reset if your device locks up, which will not erase your software.

Often when I hear about networking troubles between the PPC and PC I suggest ensuring that the network drivers for your PC are up to date.

[Mastiff]

One question: You are using WiFi, right? You don't mention what kind of a network connection you're on. If it's Bluetooth, these errors would be typical.

[michaeljc]

I can't do a soft reset. The PPC is so screwed up, that when I do the soft reset, it freezes on the opening screen (the PPC opening screen that tells the firmware number). Then I have to do a hard reset. Obviously, this seems like it would be a device problem rather than Net Remote, but I haven't had the problem unless NetRemote is installed.

Also, I am using wifi and it works reliably with IE on the PPC.

[Rob H]

What other software do you have installed on this PPC besides NetRemote?

[michaeljc]

I have no other software installed on the PPC other than Net Remote. It was bought only for the purpose of using Net Remote.

[Promixis]

I have no other software installed on the PPC other than Net Remote. It was bought only for the purpose of using Net Remote.

the problems you are having are strange :x

what os is this device runnnig?

have you done a hard reset and started from scratch?

[Mastiff]

iPqa rx1955 runs WM5, but that's not the problem. I think I know what the problem is: It has a Samsung CPU, not the regular Inte XScale. I would be willing to bet a few bucks on that as the source of the problem.

michaeljc, do you by any chance try to use direct IR? That won't work on a Samsung CPU, it will in fact crash very badly with it.

[michaeljc]

No, I am not trying to use the IR as the cpu doesn't support it. I deleted the .dll (as instructed by tech support) to keep the message from popping up saying my cpu isn't supported for IR.

I have tried from scratch too many times! Every time I have to do a hard reset, it means starting from scratch. I am thinking of selling the ipaq on ebay and buying a different PPC. It i s just that since I only seem ot have the problem when using Net Remote that worries me. Granted, I haven't done a whole lot else with it.

[dirk]

I'm sort of getting this problem as well, except I only got NR working *once*. Then the PC went into screen saver and the PPC crashed and I had to do a hard reset (iPAQ rx1950). After that no connection at all no matter what I tried. No setting seem to have been altered either.

Both machines, PC+XP and PPC are new and clean running only NR.
This is serious because we want to use this combo in systems for sale. At present it's hopeless, and as the saying goes, time is money. If we can't get this to work we'll ditch NR.

Dirk

[Rob H]

Which version of NR is this?

And where in England are you?

[dirk]

It's the version I downloaded from this site a few days ago.
I live in Bedford but am currently working near Buckingham (Milton Keynes).

Dirk

[Rob H]

Is that version 1.1.0.44 or one of the beta versions?

[dirk]

The download is named NetRemote-Pro-Suite-11-Aug-2005.exe

Dirk

[Rob H]

That's 1.1.0.44 then.

It may be worth trying the beta.

Mind you, I've never known there be a problem with 1.1.0.44 on a PC. Or was this just Mediabridge on the PC?

Are you sure your anti-virus software is up to date?

[dirk]

They are new and clean machines.
Media Bridge runs fine with NetRemote together on the PC.
What problems are fixed in the beta?

Dirk

[Rob H]

Not so much bug fixes as new features and a new internal architecture.

Can you ensure that you have the latest network drivers installed for your network card/motherboard - or possibly try with a different PC.

[Ben S]

Also, have you tried the test program discussed here (http://www.promixis.com/phpBB2/viewtopic.php?t=13499)?

[dirk]

Thanks.
We are doing two things. First, replacing the PC WiFi card (belkin) with Netgear. I'm having problems with the Belkin apart from this one so it might be of use. Will also download and run the test.
I'll post the results when I have them, either good or bad.

Dirk

[Promixis]

Thanks.
We are doing two things. First, replacing the PC WiFi card (belkin) with Netgear. I'm having problems with the Belkin apart from this one so it might be of use. Will also download and run the test.
I'll post the results when I have them, either good or bad.

Dirk


let us know...

[dirk]

OK - changed to Netgear from Belkin and at least I don't get the dropouts I was having with the main network. However, no effect on NR functionality either normal or ad hoc mode.

Downloaded the test s/w and it could not make a connection.

Then it started working after I changed socket numbers! Test worked.
For some reason in this case the PPC went through a load of screens telling me that IR was not supported?

Rebooted the PC and got the message that there was a socket clash on server startup. Got this message whether I used 20002 or 20003. No longer working.
This is a new problem.

Any idea of what is likely to be clashing?

Dirk

[Ben S]

I don't see mention here of what media player you are using?

It isn't J River is it?

When MediaBridge is not running, if you go the task manager, do you see an instance of NetRemoteServer.exe running?

[dirk]

Running WMC
And yes, I do have NRS running when it should be closed down!
What's up?

Dirk

[dirk]

Situation now is that I have 100% good connection between PC and PPC, so no problems there.

Server does not start up properly becuse of alleged socket clash on PC powerup. If I close down all instances of the server and restart it I don't get the clash message, but it still won't work.

The two times I have seen it working are not due to anything special that I can put my finger on, and the functioning has not persisted.

What I thought would be a 2 hr job has now turned into a week.

Dirk

[Ben S]

I'm confused as to what you mean that you have 100% good connection between PC and PPC? Does this mean you ran the test app and it now connects 100% of the time?

But then you say it still doesn't work. I'm confused.

Once the test app tells you it can connect (100% of the time) then we've ironed out that's it not a networking issue and we can move on to seeing what is breaking.

[dirk]

When I say connection is good, I mean between the machines eg signal strengths in ad hoc mode.

NR stuff still won't run.
The test works when NR works, and doesn't when it doesn't.
NR works intermittently and rarely, seemingly for no particular reason.
The server now constantly generates a socket clash message on PC powerup.
Situation is total non function at present.

Dirk

[Ben S]

If you're running in ad-hoc mode, are the IP addresses set always the same, or do they change? Is the NR client set to use a hostname or IP address to connect? If set to hostname, try changing it to an IP address, and disable "Use Autodiscovery" in the general properties page.

[dirk]

I've run in both ad-hoc and DHCP mode with no difference in response.

Dirk

[Ben S]

And what about the IP address instead of Host name? WM5 seems to be iffy about host names, for some reason.

[dirk]

Tried using IP addresses instead of names.
Still will not work.
Also I am persistently getting a message about clashing sockets from MB on the PC on powerup. I've uninstalled and reinstalled and that has not helped at all.
I'm running out of options here. I'm not some hobbyist with loads of time to piss about - I have to have a reliable working solution for our company *very* soon.

Dirk

[dirk]

Can I get a phone number so I can talk to someone directly?

Dirk

[Ben S]

Hi Dirk -
What would be most helpful would be the ability to either VNC or RDC into the machine you're having trouble with. This would allow us to

1. See the problem
2. Diagnose what's happening
3. Test a fix

Is this possible?

[dirk]

Having downloaded the latest beta things have improved.
I now get regular positive reports from the NR tool on the PPC as it seemingly connects to MB.
The bad news is I can't get NR running on the PPC because it now wants an authorisation code. What next?

Dirk

[Ben S]

Unfortunately this means the 30 day trial has expired. We don't have a way to extend the trial until the next beta of NetRemote 2. For a test to see if this works properly, you can set the date back on your PPC a few days.

[dirk]

Well, I bought it so I''l post tomorrow whether it works OK.
Apart from that I haven't had it 30days. I only downloaded the beta a couple of days ago. Even the original was less than a couple of weeks old IIRC

Dirk

[dirk]

Situation now, with beta installed and NR bought.
NR Utility can talk to MB.
NR cannot get a connection.
All the advice/troubleshooting stuff has not helped.
Firewall off.
What next?

Dirk

[Rob H]

What version number of Mediabridge?

[dirk]

2.2.0.55

[Rob H]

Can you check that both NR and MB are using the same port number?

[dirk]

Both set to 20003
NR Mediabridge instance = audio:20003 (-10)

[Ben S]

If the utility can get a connection and NR cannot, you need to verify that the settings in NetRemote are -exactly the same- as the utility.

If they are -exactly- the same, please send me the MediaBridge.log file from your MediaBridge directory so we can see if it's losing a connection for some reason.

Also, if you're running headless, do you need to be using MCE or is WMP okay?

[Rob H]

Do you still see it continually connecting with different port numbers?

[dirk]

Settings are identical ie name is the same and so is port number.
Also at present not running headless. In fact, I'm using the audio server to send this message.

Dirk

[dirk]

NR on the audio server connects OK with MB on the server and I can play stuff via WMP
I see no remote connection at all from PPC.

Dirk

[Ben S]

On the PPC, please go into the Configuration/Plugins tab. Open "MediaBridge", and ensure that there is only one instance, and that it's using the IP address (not host name) of the server.

If the utility can connect, then -at a minimum- NetRemote should be able to connect.

[dirk]

OK - NR works with handset addresses but still seems a bit flaky.
Why won't it work with the name?

Dirk

[dirk]

Next problems
1) Flaky connection means that volume control often does not change the sound even though the slider moves. Is there no feedback checking?

2) NR locked up. Closed the app and now it will not start again. All I get on screen is the name on the top bar.

Dirk

[Ben S]

Switch to Windows Media Player (for now) and ensure that things are not flakey. If things are still flakey, then unfortunately there is something in your environment which just is not happy with NetRemote.

To exit the app if it locked up in some way, go to the control panel, memory, running programs, tap NetRemote, and hit exit.

[dirk]

Still getting dropouts between MB/NR. The signal strength is pretty good so I don't suspect the WiFi link. This periodically causes the NR end to lock up, most especially when altering the volume control. Even when the link is good the volume slider does not track some of the time. Can any of this be put down to lack of processing power?
On lockup I have to do a hard reset most of the time. It also runs through a few popups telling me that IR control is not supported on the CPU- is there any way of getting rid of this stuff?

Dirk

[Ben S]

Yes. Remove IRHardware.dll from the NetRemote directory.

Have you tried switching to WMP to see if the experience is better?

[dirk]

Currently set up for WMP.
It also looks like we may also have to use Girder since we need to interact with a piece of s/w that configures an external sound processor via old style serial port. It would be nice to be able to alter setups from the remote.

Dirk

[Ben S]

So everything is working fine under WMP?

[dirk]

No. It's still flaky but I've got other stuff to look at for the next few days.
One Q still bothers me though - why should I have to use an address instead of the server name? presumably the s/w was designed to work with the name? Why not on my setup? And why should the beta be so much more useable (compared to zilch) than the 'official' current release?

Where's the problem - PPC or PC?

Dirk

[Ben S]

My assumption is the network is the problem. Neither version should be "flakey" so that's my guess as to the culprit.

Regarding address versus server name - Microsoft decided to change -many- things under the covers of WM5 compared to PPC2k3, and this is one of them. It simply won't do name lookups for some reason.

We're looking to correct this on our side by having autodiscovery store the IP _and_ the name and figuring out which name is which IP for you.

[dirk]

Well, the symptoms do point to the network with the link being dropped and re-acquired every couple of seconds. On MB I can see the connected address flashing on and off, with new ports often selected each time.
However, these are both brandnew, clean, machines.

Dirk

[Ben S]

If it's flashing it means there is still a problem of some sort. Can you post your latest NetRemoteServer.log (or MediaBridge.log if using the new version)?

[dirk]

An extract from the MediaBridge log is as follows:

MediaBridge: Creating server on port 20003
MediaBridge: Server attempting to start
Network: Creating both sockets
Network: Created sockets
Network: Listen thread created, now starting
Network: Listen thread started
Network: Autodiscover thread created, now started
Network: Autodiscover thread started
MediaBridge: Server started successfully
Network: Entering listen thread to poll for client connections (True)
Network: Connection found, accepting client
Network: Accepted connection from 192.168.2.4:4884
Handshake 192.168.2.4:4884: Reading Message
Handshake 192.168.2.4:4884: Read HS Message (NRPI M 1.0.1.0)
Adding client 192.168.2.4:4884 to list
Network: Client handshake successful from 192.168.2.4:4884
MediaBridge: Received command : GPN from 192.168.2.4:4884
Removing client 192.168.2.4:4884 from list
Network: Connection found, accepting client
Network: Accepted connection from 192.168.2.4:4912
Handshake 192.168.2.4:4912: Reading Message
Handshake 192.168.2.4:4912: Read HS Message ()
Network: Client handshake unsuccessful from 192.168.2.4:4912
Network: Connection found, accepting client
Network: Accepted connection from 192.168.2.4:4914
Handshake 192.168.2.4:4914: Reading Message
Handshake 192.168.2.4:4914: Read HS Message (NRPI M 1.0.1.0)
Adding client 192.168.2.4:4914 to list
Network: Client handshake successful from 192.168.2.4:4914
MediaBridge: Received command : S MP.Zone "Main Zone" from 192.168.2.4:4914
Network: Connection found, accepting client
Network: Accepted connection from 192.168.2.4:4910
Handshake 192.168.2.4:4910: Reading Message
Handshake 192.168.2.4:4910: Read HS Message ()
Network: Client handshake unsuccessful from 192.168.2.4:4910
MediaBridge: Received command : GPN from 192.168.2.4:4914
Removing client 192.168.2.4:4914 from list
Network: Connection found, accepting client
Network: Accepted connection from 192.168.2.4:4929
Handshake 192.168.2.4:4929: Reading Message
Handshake 192.168.2.4:4929: Read HS Message (NRPI M 1.0.1.0)
Adding client 192.168.2.4:4929 to list
Network: Client handshake successful from 192.168.2.4:4929
MediaBridge: Received command : S MP.Zone "Main Zone" from 192.168.2.4:4929
MediaBridge: Received command : GPN from 192.168.2.4:4929
Removing client 192.168.2.4:4929 from list
Network: Connection found, accepting client
Network: Accepted connection from 192.168.2.4:4949
Handshake 192.168.2.4:4949: Reading Message
Handshake 192.168.2.4:4949: Read HS Message (NRPI M 1.0.1.0)
Adding client 192.168.2.4:4949 to list
Network: Client handshake successful from 192.168.2.4:4949
MediaBridge: Received command : S MP.Zone "Main Zone" from 192.168.2.4:4949
MediaBridge: Received command : GPN from 192.168.2.4:4949
Removing client 192.168.2.4:4949 from list
Network: Connection found, accepting client
Network: Accepted connection from 192.168.2.4:4978
Handshake 192.168.2.4:4978: Reading Message
Handshake 192.168.2.4:4978: Read HS Message (NRPI M 1.0.1.0)
Adding client 192.168.2.4:4978 to list
Network: Client handshake successful from 192.168.2.4:4978
MediaBridge: Received command : S MP.Zone "Main Zone" from 192.168.2.4:4978
MediaBridge: Received command : GPN from 192.168.2.4:4978
Removing client 192.168.2.4:4978 from list
Network: Connection found, accepting client
Network: Accepted connection from 192.168.2.4:4994
Handshake 192.168.2.4:4994: Reading Message
Handshake 192.168.2.4:4994: Read HS Message (NRPI M 1.0.1.0)
Adding client 192.168.2.4:4994 to list
Network: Client handshake successful from 192.168.2.4:4994
MediaBridge: Received command : S MP.Zone "Main Zone" from 192.168.2.4:4994
MediaBridge: Received command : GPN from 192.168.2.4:4994
Removing client 192.168.2.4:4994 from list
Network: Connection found, accepting client
Network: Accepted connection from 192.168.2.4:1038
Handshake 192.168.2.4:1038: Reading Message
Handshake 192.168.2.4:1038: Read HS Message (NRPI M 1.0.1.0)
Adding client 192.168.2.4:1038 to list
Network: Client handshake successful from 192.168.2.4:1038
MediaBridge: Received command : S MP.Zone "Main Zone" from 192.168.2.4:1038
MediaBridge: Received command : GPN from 192.168.2.4:1038
Removing client 192.168.2.4:1038 from list
Network: Connection found, accepting client
Network: Accepted connection from 192.168.2.4:1052
Handshake 192.168.2.4:1052: Reading Message
Handshake 192.168.2.4:1052: Read HS Message (NRPI M 1.0.1.0)
Adding client 192.168.2.4:1052 to list
Network: Client handshake successful from 192.168.2.4:1052
MediaBridge: Received command : S MP.Zone "Main Zone" from 192.168.2.4:1052
MediaBridge: Received command : GPN from 192.168.2.4:1052
Removing client 192.168.2.4:1052 from list
Network: Connection found, accepting client
Network: Accepted connection from 192.168.2.4:1068
Handshake 192.168.2.4:1068: Reading Message
Handshake 192.168.2.4:1068: Read HS Message (NRPI M 1.0.1.0)
Adding client 192.168.2.4:1068 to list
Network: Client handshake successful from 192.168.2.4:1068
MediaBridge: Received command : S MP.Zone "Main Zone" from 192.168.2.4:1068
MediaBridge: Received command : GPN from 192.168.2.4:1068
Removing client 192.168.2.4:1068 from list
Network: Connection found, accepting client
Network: Accepted connection from 192.168.2.4:1083
Handshake 192.168.2.4:1083: Reading Message
Handshake 192.168.2.4:1083: Read HS Message (NRPI M 1.0.1.0)
Adding client 192.168.2.4:1083 to list
Network: Client handshake successful from 192.168.2.4:1083
MediaBridge: Received command : S MP.Zone "Main Zone" from 192.168.2.4:1083
MediaBridge: Received command : GPN from 192.168.2.4:1083
Removing client 192.168.2.4:1083 from list
Network: Connection found, accepting client
Network: Accepted connection from 192.168.2.4:1097
Handshake 192.168.2.4:1097: Reading Message
Handshake 192.168.2.4:1097: Read HS Message (NRPI M 1.0.1.0)
Adding client 192.168.2.4:1097 to list
Network: Client handshake successful from 192.168.2.4:1097
MediaBridge: Received command : S MP.Zone "Main Zone" from 192.168.2.4:1097
MediaBridge: Received command : GPN from 192.168.2.4:1097
Removing client 192.168.2.4:1097 from list
Network: Connection found, accepting client
Network: Accepted connection from 192.168.2.4:1113
Handshake 192.168.2.4:1113: Reading Message
Handshake 192.168.2.4:1113: Read HS Message (NRPI M 1.0.1.0)
Adding client 192.168.2.4:1113 to list
Network: Client handshake successful from 192.168.2.4:1113
MediaBridge: Received command : S MP.Zone "Main Zone" from 192.168.2.4:1113
MediaBridge: Received command : GPN from 192.168.2.4:1113
Removing client 192.168.2.4:1113 from list
Network: Connection found, accepting client
Network: Accepted connection from 192.168.2.4:1122
Handshake 192.168.2.4:1122: Reading Message
Handshake 192.168.2.4:1122: Read HS Message (NRPI M 1.0.1.0)
Adding client 192.168.2.4:1122 to list
Network: Client handshake successful from 192.168.2.4:1122
MediaBridge: Received command : S MP.Zone "Main Zone" from 192.168.2.4:1122
MediaBridge: Received command : GPN from 192.168.2.4:1122
Removing client 192.168.2.4:1122 from list
Network: Connection found, accepting client
Network: Accepted connection from 192.168.2.4:1130
Handshake 192.168.2.4:1130: Reading Message
Handshake 192.168.2.4:1130: Read HS Message (NRPI M 1.0.1.0)
Adding client 192.168.2.4:1130 to list
Network: Client handshake successful from 192.168.2.4:1130
MediaBridge: Received command : S MP.Zone "Main Zone" from 192.168.2.4:1130
MediaBridge: Received command : GPN from 192.168.2.4:1130
Removing client 192.168.2.4:1130 from list
Network: Connection found, accepting client
Network: Accepted connection from 192.168.2.4:1146
Handshake 192.168.2.4:1146: Reading Message
Handshake 192.168.2.4:1146: Read HS Message (NRPI M 1.0.1.0)
Adding client 192.168.2.4:1146 to list
Network: Client handshake successful from 192.168.2.4:1146
MediaBridge: Received command : S MP.Zone "Main Zone" from 192.168.2.4:1146
MediaBridge: Received command : GPN from 192.168.2.4:1146
Network: Connection found, accepting client
Network: Accepted connection from 192.168.2.4:1144
Handshake 192.168.2.4:1144: Reading Message
Handshake 192.168.2.4:1144: Read HS Message ()
Network: Client handshake unsuccessful from 192.168.2.4:1144
Removing client 192.168.2.4:1146 from list
Network: Connection found, accepting client
Network: Accepted connection from 192.168.2.4:1161
Handshake 192.168.2.4:1161: Reading Message
Handshake 192.168.2.4:1161: Read HS Message (NRPI M 1.0.1.0)
Adding client 192.168.2.4:1161 to list
Network: Client handshake successful from 192.168.2.4:1161
MediaBridge: Received command : S MP.Zone "Main Zone" from 192.168.2.4:1161
MediaBridge: Received command : GPN from 192.168.2.4:1161
Removing client 192.168.2.4:1161 from list

[Ben S]

It looks like it's having problems getting the playing now list.

Is there any chance I can RDC into your system to take a closer look?

[dirk]

We may be able to arrange that sometime next week.
Let you know when.
What is required at my end?

Dirk

[Ben S]

If running XP Pro, you just need to enable it, make sure port 3389 is allowed through your firewall, and send me the IP address, username, and password.