SDS200 with Proscan

[Chimper]

Web server set up with SDS200 and Proscan 21.2. Same problem now for years.
Works fine except for randomly and repeatedly losing contact with scanner. Re-starting scanner fixes the problem.
Lucky to go even a day with re-setting. Any help appreciated. Have trying new cables and updating router firmware.
72.2.167.15:5000

 

[bearcatrp]

Think it has something to do with windows 10 or higher. When I ran it on win7, never had this issue. Since being on win 10, lose connection about once a month, sometimes more. Would be nice to figure this out.

 

[donc13]

Web server set up with SDS200 and Proscan 21.2. Same problem now for years.
Works fine except for randomly and repeatedly losing contact with scanner. Re-starting scanner fixes the problem.
Lucky to go even a day with re-setting. Any help appreciated. Have trying new cables and updating router firmware.
72.2.167.15:5000

Are you using an assigned IP address or via DHCP? For setups like yours, a static address is preferred and obviously you need to reserve your assigned IP address for the sds 200 in your router/DHCP server.

 

[jtwalker]

I think this is totally a router related issue. Maybe static IP assignment as suggested by @donc13, maybe an automatic reboot/restart of services, maybe lease timeout, maybe something else.

Look at your router setup/config, particularly in the advanced options, for something that stands out.

 

[dave3825]

I use an assigned ip and loose connection on win 7 pro 64 bit using the vonets wifi thing. Scanner also stops playing audio and requires a reboot. But for the last 2 weeks the scanner has not been hooked to lan and has not lost audio. Was thinking it was two separate issues but now, not to sure. Have had alot going on so not really been able to troubleshoot. When I get back I am going to try it hard wired as this wireless thing I use might jus be a pos.

 

[donc13]

I use an assigned ip and loose connection on win 7 pro 64 bit using the vonets wifi thing. Scanner also stops playing audio and requires a reboot. But for the last 2 weeks the scanner has not been hooked to lan and has not lost audio. Was thinking it was two separate issues but now, not to sure. Have had alot going on so not really been able to troubleshoot. When I get back I am going to try it hard wired as this wireless thing I use might jus be a pos.

Hardwire to the front network port only.

 

[ProScan]

Web server set up with SDS200 and Proscan 21.2. Same problem now for years.
Works fine except for randomly and repeatedly losing contact with scanner. Re-starting scanner fixes the problem.
Lucky to go even a day with re-setting. Any help appreciated. Have trying new cables and updating router firmware.
72.2.167.15:5000

If you have a spare Cat 6 cable or higher, try that. I've heard one time that fixed the problem. If your computer is connected with WiFi 2.4, try using 5 GHz. I recently received an email that fixed the problem.

 

[Chimper]

Are you using an assigned IP address or via DHCP? For setups like yours, a static address is preferred and obviously you need to reserve your assigned IP address for the sds 200 in your router/DHCP server.

Assigned

Hardwire to the front network port only.

It already is.

If you have a spare Cat 6 cable or higher, try that. I've heard one time that fixed the problem. If your computer is connected with WiFi 2.4, try using 5 GHz. I recently received an email that fixed the problem.

Cat 6 and 5ghz now.

 

[ctiller]

Web server set up with SDS200 and Proscan 21.2. Same problem now for years.
Works fine except for randomly and repeatedly losing contact with scanner. Re-starting scanner fixes the problem.
Lucky to go even a day with re-setting. Any help appreciated. Have trying new cables and updating router firmware.
72.2.167.15:5000

I've had the same issue for a few months now. I'm thinking it's more an issue with my VONETS adapter I'm using, but not sure. screen on pro scan goes dark. I turn the scanner off and back on and it will usually reconnect. it seems to come at random times. Can't figure out the rhyme or reason to it

 

[Chris0516]

Think it has something to do with windows 10 or higher. When I ran it on win7, never had this issue. Since being on win 10, lose connection about once a month, sometimes more. Would be nice to figure this out.

I am inclined to agree with this. Before I upgraded to Win 11 and peace of mind. I had Win 10 and stress.

 

[ctiller]

actually thinking more about it now a few devices in my house have been doing this so it may be netgear did some kind of firmware update to my orbi system or modem.

 

[belvdr]

Never had an issue, but I keep things simple as possible: the computer and the SDS are cabled into the same switch. If you're using Wi-Fi, just expect issues.

 

[KevinC]

Never had an issue, but I keep things simple as possible: the computer and the SDS are cabled into the same switch. If you're using Wi-Fi, just expect issues.

I'm just lucky I guess. SDS200 into a Vonets for several months now and it's rock solid. But I do have a mesh WiFi network so I'm saturated RF-wise. Also have the 536 on the WiFi dongle and it's stable as well. And 3 other scanners on serial to BT adapters that are solid also (after I replaced on onboard BT adapter with a USB one).

 

[belvdr]

I'm just lucky I guess. SDS200 into a Vonets for several months now and it's rock solid. But I do have a mesh WiFi network so I'm saturated RF-wise. Also have the 536 on the WiFi dongle and it's stable as well. And 3 other scanners on serial to BT adapters that are solid also (after I replaced on onboard BT adapter with a USB one).

Sometimes it works, sometimes it doesn't. Ethernet always works. I'm one of those guys who refuses to use Wi-Fi, unless required.

 

[eaf1956]

Web server set up with SDS200 and Proscan 21.2. Same problem now for years.
Works fine except for randomly and repeatedly losing contact with scanner. Re-starting scanner fixes the problem.
Lucky to go even a day with re-setting. Any help appreciated. Have trying new cables and updating router firmware.
72.2.167.15:5000

I would use either NO IP or DYN instead of using your IP address. My No IP address for my scanners are SDS200.hopto.me:5001 or sds200.hopto.me:5003

 

[donc13]

I would use either NO IP or DYN instead of using your IP address. My No IP address for my scanners are SDS200.hopto.me:5001 or sds200.hopto.me:5003

Your local router converts those names into IP addresses. So there are IP addresses.

 

[belvdr]

Your local router converts those names into IP addresses. So there are IP addresses.

They are recommending to use a dynamic DNS service, so that FQDN will follow any public IP changes on the router. Then, you no longer have to track it manually, and can use the FQDN.

 

[donc13]

They are recommending to use a dynamic DNS service, so that FQDN will follow any public IP changes on the router. Then, you no longer have to track it manually, and can use the FQDN.

I don't know who "They" are, but I reserve addresses on my local router for my devices with either hard coded IP addresses or DNS issued addresses. They are reserved based on the device's MAC address and have "common" names associated with them.

 

[belvdr]

I don't know who "They" are, but I reserve addresses on my local router for my devices with either hard coded IP addresses or DNS issued addresses. They are reserved based on the device's MAC address and have "common" names associated with them.

"They" is the person you quoted, @eaf1956.

You're talking local IPs and DNS doesn't issue IP addresses; you probably mean DHCP. I have no idea what a "common" name is. I have never heard of that term.

Dynamic DNS is generally used for the public IP address of the router. Using a service like Dyn, you could register myhome.dynu.net to your public IP, for example 192.1.1.1. Then, you access services using myhome.dynu.net. If your public IP changes, for example to 192.2.2.2, then the dynamic DNS agent updates myhome.dynu.net to reflect that and you're covered and can still use myhome.dynu.net.

 

[donc13]

Yes, you are correct, DHCP not DNS. Common name is how you can address the device on your local network vs the actual IP address.