SDS200 - LAN??
- Thread starter nessnet
- Start date
- Status
Yup, and I recall having to enable "Remote Scanner Over IP" in a couple areas in that lower section below the virtual control head, to the left of where you do the loopback check box... page 29 in the manual discusses it.... attached.
Audio Control --> Remote Scanner Over IP tab
That screenshot is of the Remote Scanner Over IP feature. You will not see anything on the right side unless you are using RSOIP in the Client mode.
Go to the Monitor & Test tab. Set the loopback there and you shall see the right side come to life.
{edit} I see you already got it.
Proscan: I went through your list and still have no connect. I do have a active connection for the screen display, but I do not have TCP/UDP connection for Audio. I tried this on two computers one with direct net connect and one on Wi-Fi with the same result. Both were Windows 10 with current updates. Nothing else dealing with audio or scanners was running at the time of all this testing. I disabled the McAfee virus/firewall. The SDS200 shows up on the Auto Detect popup on the Audio page but would not connect. I tried the hocus pocus for the ip address that metzeric suggested with no luck. Any ideas? I wonder if Microsoft Security steps up when I disable the McAfee security. I might try looking at that tomorrow.
Did you power cycle the scanner?
I don't believe Microsoft Security will have anything to do with the problem. Don't run AVG Antivirus software as that program will break the TCP connection.
Yes, I powered the scanner several times, also every time I changed the IP selection (none, DHCP, Manual) the scanner went through a restart automatically. I was just grasping at straws with the MS Security. It seems so strange that if the scanner can be found in the lookup why it cannot connect with TCP/UDP. It just feels like there is a filter of some sorts blocking connection (a firewall maybe?) or a misconnect of the port numbers between proscan and the SDS200 audio source. But these issues are way beyond my detail knowledge, so I really need some help for exactly what to look for and correct. Thanks, Carl
The audio uses TCP and the data does not so perhaps something is blocking the TCP connection.
What ports are used by the audio service. I can try to go into my firewall and open them up...
TCP scanner port is 554
TCP computer port will change each time a new connection because it's the originator.
TCP computer port will change each time a new connection because it's the originator.
Try rebooting the router and see what happens.
Bob, thanks for your help trying to connect proscan to my sds200 audio. At this point I do not believe the issue is really a proscan issue although my use of proscan is impacted. I tried vlc and had the same inability to connect to the SDS200 and I also tried the Uniden siren iphone app. VLC was completely unsuccessful and the Siren app showed the screen changes but no audio. Earlier, I tried with the router off and the McAfee software disabled and just using the hub, but proscan kept saying unable to connect to port 50536. I could not even try the audio. I am currently using AT&T Uverse network access and they provide a complicated router with a built in firewall. I tried looking for local network filtering but could not find any. All I could find was the expected blocking of unsolicited inbound messages. I think I will call AT&T and see if they have any knowledge of local network filtering. Why can't things be easy?
Before calling AT&T, I would try this:
1. Exit VLC, Siren, & ProScan
2. Power cycle the scanner
3. Try again with VLC. Use this format -> rtsp://192.168.1.19/au:scanner.au
If still fails, perhaps try another Ethernet cable. I know the data side works but I've seen a problem like this before.
1. Exit VLC, Siren, & ProScan
2. Power cycle the scanner
3. Try again with VLC. Use this format -> rtsp://192.168.1.19/au:scanner.au
If still fails, perhaps try another Ethernet cable. I know the data side works but I've seen a problem like this before.
I have tried the vlc with the au:scanner.au with no success. I even tried the setup on a second router (not from AT&T) in the front room that wasn't connected to the internet using a different cable. Proscan connected fine, but the audio didn't connect again. Do you think it would help to reload the SDS200 firmware?
I think it's better to have one conversation then another by email because I may not know the answer. I don't know the number but I'm sure someone does. You could try calling them but I doubt they would know. Perhaps a sniffer type of program may help. Perhaps one of the network guru's can chime in.
It wouldn't hurt to try.
Bob, thanks. I agree about one stream, however, I just didn't know if there was a phone number that should not be shared on a forum.
I thought about a sniffer, but I don't have access to one and I would be spending too much time on an issue that should be corrected a different way.
I may try a reload, but before that I probably just go back to a plain audio feed. When that is working, I will go on and learn more about Proscan.
I thought about a sniffer, but I don't have access to one and I would be spending too much time on an issue that should be corrected a different way.
I may try a reload, but before that I probably just go back to a plain audio feed. When that is working, I will go on and learn more about Proscan.
Bob, I apologize for all the trouble I have caused you. Shame on me
.. Naughty Naughty. Whack (ruler on knuckles). I am sorry. I received my new SDS200 and I thought that I had updated the firmware, but when I checked today, there was a full firmware update. After the update, guess what, all worked well. The audio connected fine. I truly apologize for the trouble I caused you.
.. Naughty Naughty. Whack (ruler on knuckles). I am sorry. I received my new SDS200 and I thought that I had updated the firmware, but when I checked today, there was a full firmware update. After the update, guess what, all worked well. The audio connected fine. I truly apologize for the trouble I caused you.
It is always the little things that bite us in the backside.
Bob, I apologize for all the trouble I have caused you. Shame on me
No trouble at all. Glad it's working and good info. Now we can advise anyone else having with this kind of problem.
- Status
Similar threads
SDS100/SDS200:
Proscan WAN port forwarding
