SDS200 and proscan problem

[kb3nun]

Running a sds 200 with a new laptop and getting error code and droping connection
the source is running on port 8500
the web server is running on port 443
and the remote server is running on port 5000
below is a copy of the erros I am getting
Unable To Connect To Broadcastify Server - Error Code 9 - System.Net.Sockets.SocketException (0x80004005): No such host is known
at System.Net.Sockets.Socket.InternalEndConnect(IAsyncResult asyncResult)
at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
at System.Net.Sockets.TcpClient.EndConnect(IAsyncResult asyncResult)
at SourceClient.ConnectToServer(Object State) in \ProScan\SourceClient.vb:line 132
Error Code 10 - The operation is not allowed on non-connected sockets.

Unable To Connect To Broadcastify Server - Error Code 9 - System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target machine actively refused it [::ffff:174.127.114.11]:808
at System.Net.Sockets.Socket.InternalEndConnect(IAsyncResult asyncResult)
at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
at System.Net.Sockets.TcpClient.EndConnect(IAsyncResult asyncResult)
at SourceClient.ConnectToServer(Object State) in \ProScan\SourceClient.vb:line 130

I have also had my ISP to my home and monitored for any problems and no drop offs in signal

 

[kb3nun]

Also all windows firewalls and windows defender are turned off and i made a exception to allow the proscann software open
and have port forward also and the laptop and scanner are hard wired

 

[ProScan]

This is a Source Client error so the router Port Forwarding doesn't come into play.

This is the key:
Unable To Connect To Broadcastify Server - Error Code 9 - System.Net.Sockets.SocketException (0x80004005): No such host is known

I would double and triple check the Server IP Address is entered correctly. Try clicking the Broadcastify Auto Config. button to auto config.
If it still doesn't work then reboot the computer. Power cycle the scanner after the computer finishes rebooting.

{edit} Where do you see [::ffff:174.127.114.11]:808
"ffff" and brackets doesn't look right. It looks kind of like a IPv6 address.
{edit2} Where did the 808 come from? That's a port #.

 

[kb3nun]

This is a Source Client error so the router Port Forwarding doesn't come into play.

This is the key:
Unable To Connect To Broadcastify Server - Error Code 9 - System.Net.Sockets.SocketException (0x80004005): No such host is known

I would double and triple check the Server IP Address is entered correctly. Try clicking the Broadcastify Auto Config. button to auto config.
If it still doesn't work then reboot the computer. Power cycle the scanner after the computer finishes rebooting.

{edit} Where do you see [::ffff:174.127.114.11]:808
"ffff" and brackets doesn't look right. It looks kind of like a IPv6 address.
{edit2} Where did the 808 come from? That's a port #.

i did do the auto config with broadcastity and rebooted and everything and ipv6 is turned off
have no idea where 808 came from

 

[kb3nun]

i did do the auto config with broadcastity and rebooted and everything and ipv6 is turned off
have no idea where 808 came from

when u ping audio1.broadcastity.com it comes up the ip address

 

[ProScan]

when u ping audio1.broadcastity.com it comes up the ip address

Are you seeing the same error?
The Ping command may not be a definitive test because the Ping command works on the OSI network layer and the Source Client streaming to the Broadcastify server works on the transport layer (one layer above).

You could try a online search for " how to ping a certain port "

 

[belvdr]

Are you seeing the same error?
The Ping command may not be a definitive test because the Ping command works on the OSI network layer and the Source Client streaming to the Broadcastify server works on the transport layer.

You could try a online search for " how to ping a certain port "

ICMP, including ping (echo request and echo reply), operates at layer 3 (network) of the OSI model. The transport layer is in the same OSI model.

You cannot ping a specific port, although you can test to see if it is open with something like netcat or telnet.

The "no such host is known" leads me to believe there's a DNS issue. OP, open Command Prompt and type:

ipconfig /all

and post the results. Screenshot is fine.

 

[ProScan]

@kb3nun
Is this the IP address obtained when you did the auto config [::ffff:174.127.114.11]:808
Can you try entering in the IP address and port manually. I think you have to go to your feed details to get the IP address and port

 

[KevinC]

Are you seeing the same error?
The Ping command may not be a definitive test because the Ping command works on the OSI network layer and the Source Client streaming to the Broadcastify server works on the transport layer (one layer above).

You could try a online search for " how to ping a certain port "

The 7 deadly layers.

 

[kb3nun]

@kb3nun
Is this the IP address obtained when you did the auto config [::ffff:174.127.114.11]:808
Can you try entering in the IP address and port manually. I think you have to go to your feed details to get the IP address and port

No when I do the auto config it puts in audio1.broadcatity.com. On port 80
When u do a tracert in windows command prompt and use the audio1.broadcastity.com it comes up with that ip

 

[belvdr]

No when I do the auto config it puts in audio1.broadcatity.com. On port 80
When u do a tracert in windows command prompt and use the audio1.broadcastity.com it comes up with that ip

Did you change the port from 80 to 808? I would try 443 first and if that fails, use 80.

 

[ProScan]

No when I do the auto config it puts in audio1.broadcatity.com. On port 80
When u do a tracert in windows command prompt and use the audio1.broadcastity.com it comes up with that ip

This is what I get when doing a tracert audio1.broadcatity.com
Something is not right

---------------------------
Tracing route to hdr-nlb5-4e815dd67a14bf7f.elb.us-east-2.amazonaws.com [3.130.204.160]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms READYSHARE [192.168.0.1]
2 10 ms 14 ms 7 ms 142-254-176-225.inf.spectrum.com [142.254.176.225]
3 11 ms 13 ms 11 ms lag-55.ontrcacp01h.netops.charter.com [24.30.174.161]
4 15 ms 14 ms 22 ms lag-15.ontrcacp01r.netops.charter.com [72.129.5.214]
5 13 ms 11 ms 13 ms lag-21.lsancarc01r.netops.charter.com [72.129.5.0]
6 17 ms 15 ms 15 ms lag-16.lsancarc0yw-bcr00.netops.charter.com [66.109.6.102]
7 51 ms 47 ms 46 ms lag-21.tustca4200w-bcr00.netops.charter.com [107.14.19.36]
8 43 ms 43 ms 43 ms lag-401.dllstx976iw-bcr00.netops.charter.com [66.109.5.229]
9 43 ms 44 ms 46 ms lag-0.pr3.dfw10.netops.charter.com [66.109.5.121]

 

[ProScan]

belvdr is advising in #7

The "no such host is known" leads me to believe there's a DNS issue. OP, open Command Prompt and type:
Code:

ipconfig /all

So can you try ipconfig /all and post your results but edit out the physical addresses.

 

[kb3nun]

Did you change the port from 80 to 808? I would try 443 first and if that fails, use 80.

I changed it to port 8500 and tried port 8080 also

 

[kb3nun]

ICMP, including ping (echo request and echo reply), operates at layer 3 (network) of the OSI model. The transport layer is in the same OSI model.

You cannot ping a specific port, although you can test to see if it is open with something like netcat or telnet.

The "no such host is known" leads me to believe there's a DNS issue. OP, open Command Prompt and type:

ipconfig /all

and post the results. Screenshot is fine.

ICMP, including ping (echo request and echo reply), operates at layer 3 (network) of the OSI model. The transport layer is in the same OSI model.

You cannot ping a specific port, although you can test to see if it is open with something like netcat or telnet.

The "no such host is known" leads me to believe there's a DNS issue. OP, open Command Prompt and type:

ipconfig /all

and post the results. Screenshot is fine.

(c) Microsoft Corporation. All rights reserved.

C:\Users\ledfo>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : DESKTOP-5HG0LT8
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Ethernet:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : B4-B6-86-EC-54-47
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Local Area Connection* 1:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #3
Physical Address. . . . . . . . . : DA-9C-67-4C-3C-99
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Local Area Connection* 4:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #4
Physical Address. . . . . . . . . : FA-9C-67-4C-3C-99
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wi-Fi:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8821CE 802.11ac PCIe Adapter
Physical Address. . . . . . . . . : D8-9C-67-4C-3C-99
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::f6ab:3819:d031:4f8b%4(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.124(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Friday, December 30, 2022 9:13:39 PM
Lease Expires . . . . . . . . . . : Saturday, December 31, 2022 9:21:17 PM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 81304679
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-23-2A-D5-58-B4-B6-86-EC-54-47
DNS Servers . . . . . . . . . . . : 192.168.1.1
NetBIOS over Tcpip. . . . . . . . : Enabled

C:\Users\ledfo>

 

[kb3nun]

This is what I get when doing a tracert audio1.broadcatity.com
Something is not right

---------------------------
Tracing route to hdr-nlb5-4e815dd67a14bf7f.elb.us-east-2.amazonaws.com [3.130.204.160]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms READYSHARE [192.168.0.1]
2 10 ms 14 ms 7 ms 142-254-176-225.inf.spectrum.com [142.254.176.225]
3 11 ms 13 ms 11 ms lag-55.ontrcacp01h.netops.charter.com [24.30.174.161]
4 15 ms 14 ms 22 ms lag-15.ontrcacp01r.netops.charter.com [72.129.5.214]
5 13 ms 11 ms 13 ms lag-21.lsancarc01r.netops.charter.com [72.129.5.0]
6 17 ms 15 ms 15 ms lag-16.lsancarc0yw-bcr00.netops.charter.com [66.109.6.102]
7 51 ms 47 ms 46 ms lag-21.tustca4200w-bcr00.netops.charter.com [107.14.19.36]
8 43 ms 43 ms 43 ms lag-401.dllstx976iw-bcr00.netops.charter.com [66.109.5.229]
9 43 ms 44 ms 46 ms lag-0.pr3.dfw10.netops.charter.com [66.109.5.121]

crosoft Windows [Version 10.0.19045.2364]
(c) Microsoft Corporation. All rights reserved.

C:\Users\ledfo>tracert audio1.broadcastify.com

Tracing route to audio1.broadcastify.com [174.127.114.11]
over a maximum of 30 hops:

1 * * 10 ms router.asus.com [192.168.1.1]
2 13 ms 9 ms 17 ms bdle10-sub105.aggr2.phdl.pa.rcn.net [168.91.178.1]
3 9 ms 16 ms 8 ms hge0-0-0-21.core1.phdl.pa.rcn.net [207.172.18.77]
4 9 ms 12 ms 21 ms hge0-0-0-14.border2.phdl.pa.rcn.net [207.172.19.150]
5 14 ms 12 ms 10 ms lag-105.ear3.Newark1.Level3.net [4.71.144.225]
6 * * * Request timed out.
7 44 ms 49 ms 44 ms HOSTING-SER.ear5.Dallas1.Level3.net [4.7.207.6]
8 47 ms 44 ms 44 ms 174.127.115.5.static.midphase.com [174.127.115.5]
9 46 ms 46 ms 43 ms kidneycarenw.com [174.127.114.11]

Trace complete.

C:\Users\ledfo>

 

[belvdr]

I changed it to port 8500 and tried port 8080 also

I think that’s the local side, i.e. the streaming port on your side. For the connection to Broadcastify, what port is configured?

 

[kb3nun]

I think that’s the local side, i.e. the streaming port on your side. For the connection to Broadcastify, what port is configured?

I have port 8500 configured, default. Is port 80 when u do the auto configuration

 

[belvdr]

@ProScan is there a port configuration field for the Broadcastify side? I don’t have ProScan installed at the moment.

 

[ProScan]

I have port 8500 configured, default. Is port 80 when u do the auto configuration

Where are you getting 8500 from? It should be 80 (8080 will work too).

{edit} Can you power cycle the router if you didn't already.