Hey all.
Just for background, I have a BCP536HP using the WI-FI dongle. It connects to my home network via a newer Netgear gigabit router, that is in the next room. (In other words, very good signal strength at the scanner.) I am also using ProScan on a Windows 10 PC. The PC is located in the same room as the scanner, and connects to the same Netgear router via WI-FI.
Ever since I bought the BCD536HP, I have had issues with ProScan losing the connection to the scanner. With advice from others, and with trial-and-error, I discovered the only reliable way to re-establish the connection was to power cycle the scanner. There was no need to do anything with ProScan. It would always automatically reconnect.
I have read on this forum (and others) that this problem is not unique to me. In fact, it seems to be a fairly common one. A few months ago, I only had to power cycle the scanner about once a week. But recently, I have had to power cycle the scanner daily or more in order to restore the connection. I figured there HAD to be a reason, for this, and decided to start trying things.
Initially, I tried making changes to the devices in my current setup. I tried different (older) versions of ProScan. I made sure the Uniden had the latest firmware. Made sure the router also had the latest firmware. I tried power clearing the router, restoring factory settings, etc. Basically, nothing helped.
Finally, I tried this....
I had another OLD router sitting on a shelf collecting dust. It is a Netgear model WNDR3800, and I don't even really know where I got it. (I think I picked it up at a thrift store for a few bucks.) I added this router to my network using a hardwired connection between it and the newer Netgear gigabit router mentioned above. Without going into details about my house wiring, just be aware that this placed the WNDR3800 in the basement of my house, all the way to the opposite end from the BCD536HP. In other words, about as poor a signal strength as I can possibly achieve in my house. (Although my phone was showing the strength to be about middle of the scale.)
Of course, this now created another subnet within my house, and a new set of IP addresses. So I reconfigured the WI-FI on the scanner to connect to this new network. And I also connected the ProScan PC to the same new network as the scanner. Since I have made this change, the connection has not failed once between the BCD536HP and ProScan in over 2 weeks now. I have also moved some of my other network attached items to the same subnet as the BCP, thinking I might find something that causes a conflict. But so far there have been no ill effects.
Clearly, this experiment is about as unscientific as it gets. It does NOT pinpoint the cause of my original problem, and it probably raises more questions that it answers. But regardless, my BCD536HP connection to ProScan has now been continuously solid for the longest period since I have owned the scanner. If you are also having similar issues with keeping your BCP536HP WI-FI connection active, maybe this will help you create a work-around too.
Just for background, I have a BCP536HP using the WI-FI dongle. It connects to my home network via a newer Netgear gigabit router, that is in the next room. (In other words, very good signal strength at the scanner.) I am also using ProScan on a Windows 10 PC. The PC is located in the same room as the scanner, and connects to the same Netgear router via WI-FI.
Ever since I bought the BCD536HP, I have had issues with ProScan losing the connection to the scanner. With advice from others, and with trial-and-error, I discovered the only reliable way to re-establish the connection was to power cycle the scanner. There was no need to do anything with ProScan. It would always automatically reconnect.
I have read on this forum (and others) that this problem is not unique to me. In fact, it seems to be a fairly common one. A few months ago, I only had to power cycle the scanner about once a week. But recently, I have had to power cycle the scanner daily or more in order to restore the connection. I figured there HAD to be a reason, for this, and decided to start trying things.
Initially, I tried making changes to the devices in my current setup. I tried different (older) versions of ProScan. I made sure the Uniden had the latest firmware. Made sure the router also had the latest firmware. I tried power clearing the router, restoring factory settings, etc. Basically, nothing helped.
Finally, I tried this....
I had another OLD router sitting on a shelf collecting dust. It is a Netgear model WNDR3800, and I don't even really know where I got it. (I think I picked it up at a thrift store for a few bucks.) I added this router to my network using a hardwired connection between it and the newer Netgear gigabit router mentioned above. Without going into details about my house wiring, just be aware that this placed the WNDR3800 in the basement of my house, all the way to the opposite end from the BCD536HP. In other words, about as poor a signal strength as I can possibly achieve in my house. (Although my phone was showing the strength to be about middle of the scale.)
Of course, this now created another subnet within my house, and a new set of IP addresses. So I reconfigured the WI-FI on the scanner to connect to this new network. And I also connected the ProScan PC to the same new network as the scanner. Since I have made this change, the connection has not failed once between the BCD536HP and ProScan in over 2 weeks now. I have also moved some of my other network attached items to the same subnet as the BCP, thinking I might find something that causes a conflict. But so far there have been no ill effects.
Clearly, this experiment is about as unscientific as it gets. It does NOT pinpoint the cause of my original problem, and it probably raises more questions that it answers. But regardless, my BCD536HP connection to ProScan has now been continuously solid for the longest period since I have owned the scanner. If you are also having similar issues with keeping your BCP536HP WI-FI connection active, maybe this will help you create a work-around too.