Clients can't connect - "Client Offline Abnormal"

[geoffro316]

Can anyone help me out here?

I can see "Clients" trying to connect to my feed, but it shows what I'm assuming is an error;

"Client Offline Abnormal (an existing connection was forcibly closed by the remote)"

Some Clients can connect without any worries, but it shows this error for others. I normally only get 1 Client at a time connected so I dont think thats the issue?? Can anyone help??

Ta

Geoff
Australia

[jobes]

I often get those and I have asked this before too along with IP's that are all over.

[geoffro316]

Hmmmm, yes, its a rather dissapointing issue that keeps raising its ugly head! Most Clients only seem to be able to connect for a minute or 2, with the maximum connection so far being about 15 minutes before it "drops out!" I was thinking it might be a bandwidth issue, but I dont think this is the case anymore. If it was bandwidth, you'd get packet loss during the audio before it drops out. With my problem, the audio sounds fine, and when I run a speed test I still have plenty of bandwidth to play with. Also, I used to run Windows Media Encoder which enabled direct connection to my PC as a server (similar to Proscan) and I could have up to 7 or 8 clients connected with no problems at all! I wonder if it's an issue with the software itself???? It's starting to get really frustrating!! I'd like to promote Proscan as I think it's an awesome product, but I won't be until I can sort this problem out.



Geoffro
Gold Coast, Australia
www.moretondiver.com/livescannerfeed.html

[Bob]

One reason for the client abnormal disconnects is the connected clients running older versions. Version 1.8.4 full and free client is the most stable.

I will put in the message box the client version number after the CLIENT OFFLINE ABNORMAL message so we can see if 1.8.4 on the client side causes these problems.

Once I finish the BCD396XT and BC346XT, I can revisit this area but at this point I don't believe there's much that can be done other then switching from TCP to UDP (connectionless) protocol and ProScan managing the connections.

[NJ10]

I have been having the same problem. I have the 996 running. My connection is solid, speed tests run perfectly, and proscan is the only thing running on my computer. Have you Found a fix for this? I had no problem until a few days ago it started. Its very frustrating..

[Bob]

I had one person in the last month with the same problem. It turned out to be his router. I'm not saying ProScan not at fault here but it is problem with TCP in general.

[f1scanner]

Is this perhaps being caused by the same problem that I think is down to ISP port throttling (See viewtopic.php?f=7&t=1108)? I never see this problem connecting to a remote server before 4pm. After 4pm, it happens after ~10secs to 2mins with EVERY remote server connection i make.

Bob

[eaf1956]

I get to mess with 2 different feeds in two counties, one on XP and one VISTA. The VISTA machine wouldn't let anyone do REMOTE Scanner over IP till I opened PORT 5000 on his D-Link router. His works fine now, but while there I tried to use my feed using REMOTE SCANNER over IP and couldn't connect. When I got home I discovered the SW said it was online and fine but evidently when a Cable MODEM was reset my IP address had changed. I told PROSCAN to get my IP which changed it to the new IP and it worked fine after that. I wonder if the SW could AUTOMATICALLY get the IP address when it restarts as I have this system set to AUTO BOOT.

Ed
KC9LVX Evansville, IN Feed and helper on KNOX Co, In feed for my brother KC9LZJ