Mobile Access via Custom Port

[wrj0]

Greetings,

 

Looking for suggestions on what’s needed to enable ISY access via a mobile device on a non-standard port (as recommended by others here for improved remote access security). I’m having a problem getting my Treo 750 to access the ISY on a non-standard port. Port forwarding on the router seems to be OK, as I can remotely access the ISY on port 444 from a PC.

 

When the ISY is set for port 443, the Treo displays the appropriate certificate page, much like the PC based browser, and then allows access to the ISY for control and status. But, nothing I’ve tried allows the Treo access to the ISY when it is set to something other than port 443 (I’ve tried a few different ports).

 

Here’s the results:

https://x.x.x.x with ISY set for port 443 works fine from the Treo 750 – works great!

https://x.x.x.x with ISY set for port 443 works fine from a PC.

https://x.x.x.x:444 with ISY set for port 444 works fine from a PC not on the ISY network.

https://x.x.x.x:444 with ISY set for port 444 fails on the Treo 750. The response is a blank page on the Treo.

 

But, if I make a Bluetooth connection from a laptop to the Treo 750 for web access using the Treo as an access point, I can access the ISY at port 444 from the PC, so I’m guessing it’s not something that the service provider (ATT) is blocking.

 

I’d appreciate any suggestions. Thanks.

 

Device Revs:

Treo: WM6

ISY-99: 2.6.12

[Michel Kohanim]

Hello wrj0,

 

It might be something that treo itself is blocking. Perhaps it's using it for SNPP (default port is 444). Would you mind trying a different port such as 8443 or 40443?

 

With kind regards,

Michel

 

Greetings,

 

Looking for suggestions on what’s needed to enable ISY access via a mobile device on a non-standard port (as recommended by others here for improved remote access security). I’m having a problem getting my Treo 750 to access the ISY on a non-standard port. Port forwarding on the router seems to be OK, as I can remotely access the ISY on port 444 from a PC.

 

When the ISY is set for port 443, the Treo displays the appropriate certificate page, much like the PC based browser, and then allows access to the ISY for control and status. But, nothing I’ve tried allows the Treo access to the ISY when it is set to something other than port 443 (I’ve tried a few different ports).

 

Here’s the results:

https://x.x.x.x with ISY set for port 443 works fine from the Treo 750 – works great!

https://x.x.x.x with ISY set for port 443 works fine from a PC.

https://x.x.x.x:444 with ISY set for port 444 works fine from a PC not on the ISY network.

https://x.x.x.x:444 with ISY set for port 444 fails on the Treo 750. The response is a blank page on the Treo.

 

But, if I make a Bluetooth connection from a laptop to the Treo 750 for web access using the Treo as an access point, I can access the ISY at port 444 from the PC, so I’m guessing it’s not something that the service provider (ATT) is blocking.

 

I’d appreciate any suggestions. Thanks.

 

Device Revs:

Treo: WM6

ISY-99: 2.6.12

[wrj0]

Will do. Thanks, Michel.

I'm also going to try another router as I'm a bit suspect about port forwarding working properly on the one I've been testing.

[wrj0]

Well...after several attempts at a few different port assignments, and testing with two different routers, I was about at wit's end trying to get port forwarding to work when accessed from the Treo 750. The Treo seemed to open any web page except the ISY when assigned to a port other than 443. Several different router port forwarding tests, multiple soft resets of the Treo, clearing history, cookies, ect. all ended in the same result. Finally, I did a hard reset on the Treo and am finally able to access the ISY without any problem. Who hoo!

[Michel Kohanim]

wrj0,

 

Thanks so very much for the update! This is indeed quite interesting; perhaps the treo had the wrong useid/pwd in it? Would you be kind enough to keep and eye on it and let us know if you find any more anomalies?

 

With kind regards,

Michel

 

Well...after several attempts at a few different port assignments, and testing with two different routers, I was about at wit's end trying to get port forwarding to work when accessed from the Treo 750. The Treo seemed to open any web page except the ISY when assigned to a port other than 443. Several different router port forwarding tests, multiple soft resets of the Treo, clearing history, cookies, ect. all ended in the same result. Finally, I did a hard reset on the Treo and am finally able to access the ISY without any problem. Who hoo!

[wrj0]

Hi Michel,

 

I believe that the user ID & PW in the Treo were correct, as I checked that several times over the past few days. I suspect something got corrupted in the Internet Explorer application on the Treo that was corrected during the hard reset. Curiously, though, other https sites would work fine; I tested several during the past couple of days.

 

I'll watch the operation from both the Treo and from a PC for a while to be sure all's well again.

 

Edit: I should add that during this problem period, most of the time when the Treo 750 would try to access to ISY remotely, it would not get to the ISY login page at all. It would show the certificate page, and when that page was acknowledged, the page would go blank with the security lock Open, the status would show “Connecting…†for a few seconds, then “Opening…†for a long period (CWT parameter?), and finally the page would go blank. But, at the end of this process, the security lock would display as Closed as if the page had been properly entered. Gladly, everything is working properly now after the Treo hard reset.

 

Thanks again for the suggestions.

[Michel Kohanim]

Hello wrj0,

 

Thanks so very much for the update. It seems that lately the mobile phone manufacturers are advocating "reboot". This is what I cannot understand nor do I ever consider!

 

I got my BlackBerry Storm a month ago and have had nothing but trouble with it (very slow/sluggish). In more than one occasion they told me "this is like a computer, you have to reboot it once in a while" ... umm? Finally, last week, they said it's something you put in there and, obviously, I told them whatever I put in there is supposed to be in there. To cut the long story short, they had me uninstall the whole operating system and reinstall and restore everything. I could understand that, once in a while, desperate measures should be taken but it would not be fair to cloak "real issues" with reboot and reinstall. It still does not work properly. I am getting a replacement but I have a feeling this is all software related.

 

With kind regards,

Michel

 

Hi Michel,

 

I believe that the user ID & PW in the Treo were correct, as I checked that several times over the past few days. I suspect something got corrupted in the Internet Explorer application on the Treo that was corrected during the hard reset. Curiously, though, other https sites would work fine; I tested several during the past couple of days.

 

I'll watch the operation from both the Treo and from a PC for a while to be sure all's well again.

 

Edit: I should add that during this problem period, most of the time when the Treo 750 would try to access to ISY remotely, it would not get to the ISY login page at all. It would show the certificate page, and when that page was acknowledged, the page would go blank with the security lock Open, the status would show “Connecting…” for a few seconds, then “Opening…” for a long period (CWT parameter?), and finally the page would go blank. But, at the end of this process, the security lock would display as Closed as if the page had been properly entered. Gladly, everything is working properly now after the Treo hard reset.

 

Thanks again for the suggestions.

[MikeB]

but I have a feeling this is all software related

 

It is. All these smart phones suck as phones. It amazes me how slow and sluggish it is sometimes on my Treo 750 when all I want to do is pick up or make a phone call. Phone calls should be priority #1! Everything else should stop, but it doesn't. It's becoming the norm, however, so people will get used to it.

 

It's not uncommon for me to have to yank my battery and reboot my Treo 750 once every week or 2.

 

Reminds me of one of the things I liked about AmigaOS - the user was #1 priority. When you used the UI, everything else running would take a back seat to the user - the user comes first.

 

Something Microsoft hasn't figured out yet.

[ulrick65]

Hello wrj0,

 

Thanks so very much for the update. It seems that lately the mobile phone manufacturers are advocating "reboot". This is what I cannot understand nor do I ever consider!

 

I got my BlackBerry Storm a month ago and have had nothing but trouble with it (very slow/sluggish). In more than one occasion they told me "this is like a computer, you have to reboot it once in a while" ... umm? Finally, last week, they said it's something you put in there and, obviously, I told them whatever I put in there is supposed to be in there. To cut the long story short, they had me uninstall the whole operating system and reinstall and restore everything. I could understand that, once in a while, desperate measures should be taken but it would not be fair to cloak "real issues" with reboot and reinstall. It still does not work properly. I am getting a replacement but I have a feeling this is all software related.

 

With kind regards,

Michel

 

 

I got my new Blackberry Storm the first day it was released and it was terrible slow...etc. etc. However, I upgraded to the new revision when it came out a couple weeks ago and it has made a HUGE improvement. I have not had to reboot once since doing this.

 

Did you update to 4.7.0.75 yet?

[Michel Kohanim]

Hi Eric,

 

Yes, I have upgraded to 4.7.0.75. They even had me reinstall the WHOLE operating system. Right now, it's even worse:

1. I can never manage to hold it at the right angle to have the keyboard show up correctly. In most cases, I get two keyboards

2. The back light starts flickering in the dark

3. On receiving calls, it goes to speaker phone by itself and then it reverts to handset by itself

4. And - I MUST TOTALLY AGREE WITH MIKE - making a phone call is the SLOWEST: the time it takes to load the keyboard is almost 3-5 seconds every time. A phone should be a phone!

 

I will let you know if the replacement is any better.

 

With kind regards,

 

Hello wrj0,

 

Thanks so very much for the update. It seems that lately the mobile phone manufacturers are advocating "reboot". This is what I cannot understand nor do I ever consider!

 

I got my BlackBerry Storm a month ago and have had nothing but trouble with it (very slow/sluggish). In more than one occasion they told me "this is like a computer, you have to reboot it once in a while" ... umm? Finally, last week, they said it's something you put in there and, obviously, I told them whatever I put in there is supposed to be in there. To cut the long story short, they had me uninstall the whole operating system and reinstall and restore everything. I could understand that, once in a while, desperate measures should be taken but it would not be fair to cloak "real issues" with reboot and reinstall. It still does not work properly. I am getting a replacement but I have a feeling this is all software related.

 

With kind regards,

Michel

 

 

I got my new Blackberry Storm the first day it was released and it was terrible slow...etc. etc. However, I upgraded to the new revision when it came out a couple weeks ago and it has made a HUGE improvement. I have not had to reboot once since doing this.

 

Did you update to 4.7.0.75 yet?