ProScan: Official Software Thread

[ProScan]

Version 22.12


1. Bytes TX increase, Bytes RX does not change
2. Networx Monitor reporting outbound data

Client Connections shows the 3 I test connected with a laptop on work wifi early this afternoon, now late night. That laptop is home and off and still shows the connection. If I stop and start it again, the test connections go away and the Networx Monitor outbound data drops off.

Thankls for the info. I'll wait and see if anyone else has a problem on this.

{edit} It sounds like there is an active connection. I would double and triple check. Perhaps ping the IP address that is showing in the Client Connection tab. The TCP protocol doesn't send data to just nowhere but only to TCP far side connection. The TCP protocol will timeout and close the connection if the far side is not reachable.

 

[Rotorhead124]

I am almost bald from pulling my hair out trying to get ProScan to connect and retain a LAN connection. It worked once for a day, but now it will connect intermittently for a few seconds but drop the connection almost immediately. It will not auto-detect the scanner on the LAN that has a fixed IP of 192.168.2.200. Surely I'm not the only one to experience this. Has anyone else cracked this nut? This functionality is what I bought the licence for, and can't make it work.

 

[03msc]

I am almost bald from pulling my hair out trying to get ProScan to connect and retain a LAN connection. It worked once for a day, but now it will connect intermittently for a few seconds but drop the connection almost immediately. It will not auto-detect the scanner on the LAN that has a fixed IP of 192.168.2.200. Surely I'm not the only one to experience this. Has anyone else cracked this nut? This functionality is what I bought the licence for, and can't make it work.

I'm not a networking expert but do you have the other computer you're trying to connect to it from in the same 192.168.2.xxx range?

Otherwise I'm thinking VLANs, firewall, or something (on the computer or on the network) is keeping the scanner and computer from seeing each other.

 

[Rotorhead124]

Oh, yes they are on the same net. The frustrating bit is that it will work, and then stop working.

 

[kruser]

Any wireless involved on the 192.168.2.xxx segment?

 

[Rotorhead124]

Yes

 

[kruser]

Yes

Can you try a cabled connection to the scanner and the computer to rule out wireless as the issue?
You can also run a continuous ping for a few minutes to see if you have some type of intermittent wireless issue. Ping -t 192.168.2.200 from a computer on the same LAN segment. End it with a Ctrl-C to see the final results.

 

[kruser]

I'm assuming you have power cycled the scanner when things go south!

 

[03msc]

Yeah, and I was going to suggest trying from a different device. In other words, if you've been trying from one computer then try it from your phone or something.

 

[Rotorhead124]

It is on a Cat 6e cable to the router.

 

[Rotorhead124]

The ping hits about one time out of 15. the rest are timed out. I wonder if the LAN port on the SDS200 is borked

 

[KevinC]

The ping hits about one time out of 15. the rest are timed out. I wonder if the LAN port on the SDS200 is borked

Have you tried a different cable? Or port on the router?

Do you have anything else on the router you could ping as a test?

 

[Rotorhead124]

Yup done all of that. I even connected it to a different switch. I have a 16 port and a 4 port.

 

[Rotorhead124]

When I set the Scanner to get the IP from the DHCP. It just sticks with the previous one. Even if it does not answer the ping. If I manually set the IP. No better. The MAC address only shows occasionally on the router management pages.

 

[Rotorhead124]

....and just like that, all by itself, It started working

 

[03msc]

I'm not saying it isn't the scanner but it sounds like a network config thing to me...somehow it was auto-blocking it or something? Saw it as a threat or 'attack' and was blocking it?

Sounds like you know networking and have a more complex setup than most with just a basic router/switch/wifi combo. I've fought with some IOT devices before that the network security in the network config was blocking because it saw their traffic as potentially threatening. Had to whitelist it and it worked.

 

[Rotorhead124]

Yeah, I have Three Switches downstream from the Router/Modem, and copious devices.

 

[Rotorhead124]

I'm not saying it isn't the scanner but it sounds like a network config thing to me...somehow it was auto-blocking it or something? Saw it as a threat or 'attack' and was blocking it?

Sounds like you know networking and have a more complex setup than most with just a basic router/switch/wifi combo. I've fought with some IOT devices before that the network security in the network config was blocking because it saw their traffic as potentially threatening. Had to whitelist it and it worked.

Well, it seems like I have it hitting the pings more often than not now. There is a lot of traffic on my network. I had made an IP reservation for 192.168.2.200 for the scanner, and it never once picked that up from the DHCP. DHCP did nothing. When I set a fixed IP of 192.168.2.200 on the scanner, I was getting nowhere, until I released the reservation. Even then it was missing more than hitting. So now that I have set it to fixed on the SDS200 at 192.168.2.5 it seems to be much better. ¯\_(ツ)_/¯

 

[ProScan]

The ping hits about one time out of 15. the rest are timed out. I wonder if the LAN port on the SDS200 is borked

Take a look at the lights on the scanner ethernet port. The amber light should be solid and the green flashes. Jiggle the cable and see if the amber light blinks.

 

[Rotorhead124]

No, it's solid.