Unable to connect to remote host problem

[kdeuser]

Hello and festive greetings to all,

I am trying with no success to view Live tv on my local network with the following address copy/pasted into browser :

http: //192.168.99.130:8002/cgi-bin/reelhttp.sh?rbc

I used this ip because together with 192.168.1.33 are the one`s which let me view the http page but not the tv.

However, keep getting the Unable to connect to remote host: Connection refused text.

So there must be something that is preventing my ip address being recognized / read.

I am also a member of a friendly German forum called ( vdr-portal ) of which i carry the same username should you wish to follow up.

The whole link is here with attachments :

http://www.vdr-portal.de/board16-vid...used/?bc384cd7

I have some information from them but am unable to understand exactly what they mean . Here is the message :

please check your streamdevhost.conf with this entry 192.168.99.0/24
and all entries (setup.conf) to the streamdev-server plugin

Way out of depth here , have never streamed any tv let alone live tv or video from pc to phone.

Really could use some help which is sorely needed.

Thanks.

[GreyGeek]

IF your TV is a "smart" TV then you should be able to configure it to accept the request from that IP.

[wizard10000]

kdeuser, there may be other things but the thing that stands out to me is your subnet mask is broken. 192.168.1 and 192.168.99 are two different networks and without some routing table magic that's beyond the scope of this thread there's no way I can see that the two networks can talk to each other without a different subnet mask.

If the server is on 192.168.99 and the clients are on 192.168.1 they're never gonna talk to each other. The way to resolve this is to put the machines on the same network; with a subnet mask of /24 only machines on the 192.168.99 network are going to be able to see the server. So - either move the server or move the client(s). Right now they're not on the same network

cheers -

[kdeuser]

@ GreyGeek,

Thanks for replying.

No, it is not a smart tv , it is a type of htpc aka glorified vdr.

@wizard10000,

There seems to be weight in your answer , but i am so sorry that i do not understand it too well.

The client and server need to be on the same network so which ip would you use ? and where in :

please check your streamdevhost.conf with this entry 192.168.99.0/24
and all entries (setup.conf) to the streamdev-server plugin

Would those changes go ?

Below are some screen shots of where these rules might go.



Many Thanks.

[kdeuser]

Hello wizard10000,

I placed 192.168.99.0/24 in all those screen shots less the setup.conf ( i just do not know where to start ) and then entered :

http://192.168.99.0/24:8002/cgi-bin/reelhttp.sh

...and unable to connect - still ...

Thanks again for helping.

[wizard10000]

Hello wizard10000,

I placed 192.168.99.0/24 in all those screen shots less the setup.conf ( i just do not know where to start ) and then entered :

http://192.168.99.0/24:8002/cgi-bin/reelhttp.sh

...and unable to connect - still ...

Thanks again for helping.

Although your server is on 192.168.99 your PC is still on 192,168,1 - until you get the PC's IP address to be somewhere between 192.168.99.1 through 192.168.1.254 it's not gonna work. Alternatively you can move the server so it's on the 192.168.1 network - it's up to you

cheers -

[oshunluvr]

I'm no network expert, but there are ways to do this. Wizard1000 is trying to tell you that 192.128.1.0/24 will never connect to 192.168.99.0/24 without some help.

It seems to me your DVR is broadcasting on two networks, which wouldn't be too odd, but you would think they would have documentation.

You could change the subnet to allow connection - can be taxing on your network though. Explanation: Using a subnet of 255.255.255.0 means your IP can connect to 192.168.1.1 thru 192.168.1.255. This equals 192.168.1.0/24 and allows 254 addresses. But if you use a subnet of 255.255.128.0 you would be able to connect to 192.168.0.0 to 192.168.127.255 or 192.168.0.0/17. This is 32766 addresses. I have no experience doing this, but you could try.

Probably a more correct way to do this would be to create an alias connection to the second subnet and add a route to directly to the dvr. Explanation: Create a pseudo network device in /etc/network/interfaces on the 192.168.99.0/24 subnet and then a route to the dvr. Check out http://www.penguintutor.com/linux/ne...alias-tutorial

Of course, none of this will mean you get to watch TV on your browser. You might be better off with an application designed to do this, like Kaffeine

[kdeuser]

Hello oshunluvr,

I do not understand a word you said.

The link you gave is just fine for someone who knows their nat from their byte but i am no where near that level.

The address used at the moment to try and connect via http is :

http://192.168.99.130:8002/cgi-bin/reelhttp.sh

You said in your answer that by substituting my ip address 192.168.99.130 with 255.255.128.0 - that would solve the problem.

So my new address would be :

http://255.255.128.0:8002/cgi-bin/reelhttp.sh

However, this does not work as i still get the connection unavailable.

Could i just point you to a link in vdr-portal . This is a friendly German forum that runs my os and there seems to be a definitive solution.

...But it`s in German ...Google is not upto the job this time although someone very trained like yourself might know how to interpret the information.

Please, if you would just take a look and see if you can make sense of it

Thanks .

http://www.vdr-portal.de/board16-vid...1/#post1253324

[oshunluvr]

You said in your answer that by substituting my ip address 192.168.99.130 with 255.255.128.0 - that would solve the problem.

No, I did not. I said using a SUBNET of 255.255.128.0 might work. That is not an IP address. Subnet refers to SUBNET MASK or MASK. The subnet mask masks an IP address, and divides the IP address into network address and host address reducing the MASK increase the available IP connections. A subnet mask of 255.255.255.0 only allows you to connect to the 254 IP addresses in your range - as both I and Wizard1000 said. If you type ifconfig into a terminal, you'll see something like:

[FONT=monospace][COLOR=#000000]enp0s31f6 Link encap:Ethernet  HWaddr 4c:cc:6a:68:62:5b                                                                                                                 [/COLOR]
         inet addr:192.168.1.199  Bcast:192.168.1.255  Mask:255.255.255.0                                                                                              
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1                                                                                                            
         RX packets:2071430 errors:0 dropped:272 overruns:0 frame:0
         TX packets:915213 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000  
         RX bytes:1861385329 (1.8 GB)  TX bytes:141330438 (141.3 MB)
         Interrupt:16 Memory:de300000-de320000 
[/FONT]

Note inet addr and mask. They are not the same thing. inet addr = IP and mask = subnet.

The link I posted is a tutorial. If you read it and attempt to follow it, you may get the result you're looking for. All you would have to do is substitute your DVR ip for the one in the tutorial. You need to connect 192.168.1.0 with 192.168.99.0 so use those IP addresses.

I realize you're a little out of your depth here, but you could do yourself a great service by carefully reading what replies you get, attempting to understand them - even if that means doing some searching and reading, then asking more questions. Bottom line is if you want to go beyond default networking you have to learn some new stuff.