Perfect and thank you!
Have a great weekend.
Your welcome. Have a great weekend too.
Perfect and thank you!
Have a great weekend.
These are the ones I know I cannot connect too.
kc9lvx.dyndns.org on port 5000
kc9lzj.ham-radio-op.net on port 4500
Any other seems okay for me.
I would bet he let his DynDNS run out, I know on mine (no-ip.org) I have to go to their page once a month and do a captcha to keep it up and running. You may try emailing him, his email is posted on his qrz page if you can not see it message me and I will send it to you.
The 1st one is mine and it should work. The other one is my brother Mike and we (meaning I) am always driving up there to work on that feed. At the current time assuming he hasn't changed anything it should be working. He keeps changing ISP's and Cable modems and routers and I constantly have to adjust which ports are able to be used. But, as far as I know both of the feeds are working at this time. Some of the problems with kc9lvx.dyndns.org is that I sometimes forget to log onto the DYN site to keep it active (Every 30 days) I will check them both out as soon as I get off of RR.
kc9lvx
So.... what the heck is this all about??
![]()
As far as kc9lzj, I guess I will have to drive the 100 mile roundtrip to see what he did this time.
Give teamviewer a try it is a great program and free for non-commercial use. Save you many miles! and it is so easy to use on both sides (no router setup or anything)
I have to log into his router and cable modem and check the port triggers and the local IP address of his feed computer. Seems to change every time the modem resets or the router resets. Tried to have it permanently assigned the same IP but his router doesn't want to do that. It also involves OPEN PORT check from his IP address just to verify the server can be seen. And no I can't talk him through it, God knows I have tried.
http://ninite.com/teamviewer/
Ok the IP address changed on the FEED computer and I had to redo the port triggering to that IP. As of right this moment it is working.
Another issue hmmm Proscan update showed port 5001 but I was using 5000. Manually changed my client to 5000 and it worked. Changed the server to 5001 just so they match and it works. So now I guess I will just leave it at port 5001 on the server side because for whatever reason the client sees 5001 even with the server set to 5000 and doing the update button.
As far as kc9lzj, I guess I will have to drive the 100 mile roundtrip to see what he did this time.
Bob is aware of this issue as I had the same problem. Norton is supposed to be fixing their database in a future update. Bob says it is a false positive.
Norton no longer gives this VIRUS alert! I just tried it.
Yours is back up and working.. Thanks for putting it back up, gonna help me through some work nights. lol
Norton no longer gives this VIRUS alert! I just tried it.
I put some conventional channels online for Vanderburgh County they may or may not remain depends on how they work out. A lot of the fire repeaters have iffy reception. Mostly it runs on a YAGI pointing North toward the Evansville Safe_T tower and it is 800 MHz. (It's a 800 MHz Yagi)
Sweet, I live out in Vanderburgh county so the volly fire tac channels are my favorite. lol
Your welcome. Have a great weekend too.
I have not looked at this thread in a while because I thought Bob was not going to do anything right now with the 536/436HPs because of his time constraints. I love ProScan and use it quite a bit for my 996XT. Just happened to look again and I see that you (Bob) are moving quite rapidly on the 536HP version. Looks very impressive, and now I am very excited. Thanks so much for spending the time Bob to do this. It will make the new x36HP experience that much more enjoyable.
Steve AA6IO