Problems with internal server to the network.

Post new topic   Reply to topic    DD-WRT Forum Index -> Atheros WiSOC based Hardware
Goto page Previous  1, 2, 3  Next
Author Message
jwoods
DD-WRT User


Joined: 13 Mar 2016
Posts: 403

PostPosted: Thu May 26, 2016 6:47    Post subject: Reply with quote
Frakko wrote:

Excuse me but I have no experience about.
Forwarding of all ports is not the same thing?
It should still work?
It operates normally if the connection is wireless. If I connect via eth wrong. It is not a strange behavior?


Forwarding all ports is not the same thing...

In order to connect via ethernet, you would need to have an ethernet cable going from the Mediabox to the router, just like having an ethernet cable going from a computer to the router.

I don't use a wired connection to my set top box, it is wireless through the router. It has a static IP address assigned in the router, and it is configured to use that static IP address on the set top box.

Port forwarding has nothing to do with the type of connection (wired/wireless)...in my case it's what applications on the set top box use to communicate with the Internet via the router.

It's also what certain games use, and some servers.

See the screenshot I posted above...my DIRECTV set top box only has ports 27177 to 27178 forwarded.

I would need approximately a 40 ft ethernet cable running from my router to the set top box to have a wired connection. Not practical.

Your situation may be different.
Sponsor
Frakko
DD-WRT Guru


Joined: 06 May 2016
Posts: 521

PostPosted: Thu May 26, 2016 7:16    Post subject: Reply with quote
I have the Mediabox and the PC connected via eth. The Mediabox I assigned the static IP. I also tried again forwarding but mediabox server is not working. I do not understand why this situation. I confirm that the problem does not arise if i connect PC and devices via wireless. Help me.
mrjcd
DD-WRT Guru


Joined: 31 Jan 2015
Posts: 6286
Location: Texas

PostPosted: Thu May 26, 2016 12:16    Post subject: Reply with quote
Just to note when assigning static leases:
Most all devices will have different MAC for wired connection....
Therefore your device would get a different IP from DHCP on ethernet and different IP on wireless.
Frakko
DD-WRT Guru


Joined: 06 May 2016
Posts: 521

PostPosted: Thu May 26, 2016 16:04    Post subject: Reply with quote
No, the ip of the mediabox is static and is the same whether I connect via wifi that eth. I also checked in the browser screen (because I do ip directly in the address bar) .The mediabox does not have the built-in wifi and there it externally not added.
So the IP may not vary. It seems a mystery ... Sad
jwoods
DD-WRT User


Joined: 13 Mar 2016
Posts: 403

PostPosted: Thu May 26, 2016 19:32    Post subject: Reply with quote
Frakko wrote:
No, the ip of the mediabox is static and is the same whether I connect via wifi that eth. I also checked in the browser screen (because I do ip directly in the address bar) .The mediabox does not have the built-in wifi and there it externally not added.
So the IP may not vary. It seems a mystery ... Sad


Then how do you connect "wirelessly"?

What @mrjcd said above is correct.

If I need to connect to a device like a network printer both wired and wireless, I need to set up two static IP addresses, because the network printer has a unique MAC for each connection type.

I would suggest you find someone locally who is knowledgeable to actually come in and look at your setup.
h8red
DD-WRT Guru


Joined: 28 Jun 2011
Posts: 580
Location: Vilnius, Lithuania

PostPosted: Thu May 26, 2016 20:32    Post subject: Reply with quote
Frakko wrote:
No, the ip of the mediabox is static and is the same whether I connect via wifi that eth. I also checked in the browser screen (because I do ip directly in the address bar) .The mediabox does not have the built-in wifi and there it externally not added.
So the IP may not vary. It seems a mystery ... :(

Tried to help you in advanced networking forum.
Can you ping any LAN-LAN device at all? Test it

_________________
[Ramips] Nexx WT3020F Openwrt @kernel #4.14.167 (OpenVPN server, Wireguard server, AD blocking, SQM QOS, USB)
jwoods
DD-WRT User


Joined: 13 Mar 2016
Posts: 403

PostPosted: Thu May 26, 2016 20:56    Post subject: Reply with quote
h8red wrote:
Frakko wrote:
No, the ip of the mediabox is static and is the same whether I connect via wifi that eth. I also checked in the browser screen (because I do ip directly in the address bar) .The mediabox does not have the built-in wifi and there it externally not added.
So the IP may not vary. It seems a mystery ... Sad

Tried to help you in advanced networking forum.
Can you ping any LAN-LAN device at all? Test it


Duplicate thread here...

http://www.dd-wrt.com/phpBB2/viewtopic.php?t=301643

Please keep in one thread...it wastes peoples time not knowing what has been posted elsewhere.
Frakko
DD-WRT Guru


Joined: 06 May 2016
Posts: 521

PostPosted: Fri May 27, 2016 4:20    Post subject: Reply with quote
[quote="jwoods"][quote="Frakko"]No, the ip of the mediabox is static and is the same whether I connect via wifi that eth. I also checked in the browser screen (because I do ip directly in the address bar) .[b]The mediabox does not have the built-in wifi and there it externally not added.[/b]
So the IP may not vary. It seems a mystery ... Sad[/quote]

Then how do you connect "wirelessly"?

What @mrjcd said above is correct.

If I need to connect to a device like a network printer both wired and wireless, I need to set up [u]two[/u] static IP addresses, because the network printer has a [u]unique MAC for each connection type[/u].

I would suggest you find someone locally who is knowledgeable to actually come in and look at your setup.[/quote]

You're confusing. The Mediabox is connected only by eth and has only interface eth. Can not connect mediabox via wifi.
From the router to arrival mediabox exclusively through eth.
The devices, smartphones and tablets connect to the router only through wifi and if I try, through them, to connect the mediabox this works normally.
The PC has the ability to connect via wifi or eth. In the first case mediabox meets regularly in the second not.
I hope that this clarification is helpful.
jwoods
DD-WRT User


Joined: 13 Mar 2016
Posts: 403

PostPosted: Fri May 27, 2016 5:00    Post subject: Reply with quote
Frakko wrote:


You're confusing. The Mediabox is connected only by eth and has only interface eth. Can not connect mediabox via wifi.


I think you're the one who is confused. Re-read your own posts...

Frakko wrote:
- Tp-Link 841ND -
I have mediabox LX1, for television vision.
Mediabox is not accessible from PCs that are connected via eth. Via WiFi connected devices are able to use the services offered by the Mediabox server


Frakko wrote:
Okay. Could you show me a screenshot with your configuration? Please.

If I connect via wifi network with my device the mediabox server is operating normally and the server enables the display of contenuti.Non understand why eth through the server on mediabox can not be reached.


Frakko wrote:
I tried to connect your computer via wifi and mediabox works.


Frakko wrote:

Excuse me but I have no experience about.
Forwarding of all ports is not the same thing?
It should still work?
It operates normally if the connection is wireless. If I connect via eth wrong. It is not a strange behavior?


Frakko wrote:
I have the Mediabox and the PC connected via eth. The Mediabox I assigned the static IP. I also tried again forwarding but mediabox server is not working. I do not understand why this situation. I confirm that the problem does not arise if i connect PC and devices via wireless. Help me.
Frakko
DD-WRT Guru


Joined: 06 May 2016
Posts: 521

PostPosted: Fri May 27, 2016 5:20    Post subject: Reply with quote
[quote="h8red"][quote="Frakko"]No, the ip of the mediabox is static and is the same whether I connect via wifi that eth. I also checked in the browser screen (because I do ip directly in the address bar) .The mediabox does not have the built-in wifi and there it externally not added.
So the IP may not vary. It seems a mystery ... Sad[/quote]
Tried to help you in advanced networking forum.
Can you ping any LAN-LAN device at all? Test it[/quote]

When you are connected via WiFi to ping the connection they are functioning. When they are connected via eth not go nowhere. I confirm ....

Mediabox: 192.168.1.138
other device: 192.168.1.5
my pc: 192.168.1.3

Microsoft Windows [Versione 10.0.10586]
(c) 2015 Microsoft Corporation. Tutti i diritti sono riservati.

C:\Users\ut>ping 192.168.1.138

Esecuzione di Ping 192.168.1.138 con 32 byte di dati:
Risposta da 192.168.1.138: byte=32 durata=2ms TTL=64
Risposta da 192.168.1.138: byte=32 durata=2ms TTL=64
Risposta da 192.168.1.138: byte=32 durata=2ms TTL=64
Risposta da 192.168.1.138: byte=32 durata=3ms TTL=64

Statistiche Ping per 192.168.1.138:
Pacchetti: Trasmessi = 4, Ricevuti = 4,
Persi = 0 (0% persi),
Tempo approssimativo percorsi andata/ritorno in millisecondi:
Minimo = 2ms, Massimo = 3ms, Medio = 2ms

C:\Users\ut>

Microsoft Windows [Versione 10.0.10586]
(c) 2015 Microsoft Corporation. Tutti i diritti sono riservati.

C:\Users\ut>ping 192.168.1.138

Esecuzione di Ping 192.168.1.138 con 32 byte di dati:
Risposta da 192.168.1.3: Host di destinazione non raggiungibile.
Risposta da 192.168.1.3: Host di destinazione non raggiungibile.
Risposta da 192.168.1.3: Host di destinazione non raggiungibile.
Risposta da 192.168.1.3: Host di destinazione non raggiungibile.

Statistiche Ping per 192.168.1.138:
Pacchetti: Trasmessi = 4, Ricevuti = 4,
Persi = 0 (0% persi),

C:\Users\ut>ping 192.168.1.5

Esecuzione di Ping 192.168.1.5 con 32 byte di dati:
Risposta da 192.168.1.5: byte=32 durata=376ms TTL=64
Risposta da 192.168.1.5: byte=32 durata=106ms TTL=64
Risposta da 192.168.1.5: byte=32 durata=115ms TTL=64
Risposta da 192.168.1.5: byte=32 durata=123ms TTL=64

Statistiche Ping per 192.168.1.5:
Pacchetti: Trasmessi = 4, Ricevuti = 4,
Persi = 0 (0% persi),
Tempo approssimativo percorsi andata/ritorno in millisecondi:
Minimo = 106ms, Massimo = 376ms, Medio = 180ms
Frakko
DD-WRT Guru


Joined: 06 May 2016
Posts: 521

PostPosted: Fri May 27, 2016 5:23    Post subject: Reply with quote
[i]to jwoods[/i]

When i'm connected via WiFi to ping the connection they are functioning. When they are connected via eth not go nowhere. I confirm ....
I use translate.google.it. probably the translation is not accurate.
Frakko
DD-WRT Guru


Joined: 06 May 2016
Posts: 521

PostPosted: Fri May 27, 2016 5:47    Post subject: Reply with quote
[quote="jwoods"][quote="h8red"][quote="Frakko"]No, the ip of the mediabox is static and is the same whether I connect via wifi that eth. I also checked in the browser screen (because I do ip directly in the address bar) .The mediabox does not have the built-in wifi and there it externally not added.
So the IP may not vary. It seems a mystery ... Sad[/quote]
Tried to help you in [b]advanced networking forum[/b].
Can you ping any LAN-LAN device at all? Test it[/quote]

Duplicate thread here...

http://www.dd-wrt.com/phpBB2/viewtopic.php?t=301643

Please keep in one thread...it wastes peoples time not knowing what has been posted elsewhere.[/quote]

I have to cancel the other tread?
jwoods
DD-WRT User


Joined: 13 Mar 2016
Posts: 403

PostPosted: Fri May 27, 2016 7:43    Post subject: Reply with quote
Frakko wrote:
to jwoods

When i'm connected via WiFi to ping the connection they are functioning. When they are connected via eth not go nowhere. I confirm ....
I use translate.google.it. probably the translation is not accurate.


In Microsoft Windows...

In a Command prompt, run tracert 192.168.1.138 for both wireless and ethernet and save the output for comparison.

Run ipconfig /all and save the output for comparison.

In Start > Settings > Network & Internet...

Check the property settings for the wireless and ethernet adapters for differences.

Check to see if your wireless connection is set to Home or Work, and your ethernet connection is set to Public.

Check if Network Discovery is turned off for the ethernet connection.

Check that all devices on the local network are in the same subnet (normally something like 255.255.255.0).
Frakko
DD-WRT Guru


Joined: 06 May 2016
Posts: 521

PostPosted: Fri May 27, 2016 11:24    Post subject: Reply with quote
Microsoft Windows [Versione 10.0.10586]
(c) 2015 Microsoft Corporation. Tutti i diritti sono riservati.

C:\Users\ut>ipconfig /all

Configurazione IP di Windows

Nome host . . . . . . . . . . . . . . : PC.Win
Suffisso DNS primario . . . . . . . . :
Tipo nodo . . . . . . . . . . . . . . : Ibrido
Routing IP abilitato. . . . . . . . . : No
Proxy WINS abilitato . . . . . . . . : No
Elenco di ricerca suffissi DNS. . . . : Home

Scheda Ethernet Ethernet:

Stato supporto. . . . . . . . . . . . : Supporto disconnesso
Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Indirizzo fisico. . . . . . . . . . . :
DHCP abilitato. . . . . . . . . . . . : Sì
Configurazione automatica abilitata : Sì

Scheda LAN wireless Connessione alla rete locale (LAN)* 11:

Stato supporto. . . . . . . . . . . . : Supporto disconnesso
Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : Scheda virtuale Microsoft Wi-Fi Direct
Indirizzo fisico. . . . . . . . . . . :
DHCP abilitato. . . . . . . . . . . . : Sì
Configurazione automatica abilitata : Sì

Scheda LAN wireless Wi-Fi:

Suffisso DNS specifico per connessione: Home
Descrizione . . . . . . . . . . . . . : Qualcomm Atheros AR9485WB-EG Wireless Network Adapter
Indirizzo fisico. . . . . . . . . . . :
DHCP abilitato. . . . . . . . . . . . : Sì
Configurazione automatica abilitata : Sì
Indirizzo IPv6 locale rispetto al collegamento . : (Preferenziale)
Indirizzo IPv4. . . . . . . . . . . . : 192.168.1.4(Preferenziale)
Subnet mask . . . . . . . . . . . . . : 255.255.255.0
Lease ottenuto. . . . . . . . . . . . : venerdì 27 maggio 2016 13.12.52
Scadenza lease . . . . . . . . . . . : sabato 28 maggio 2016 13.12.52
Gateway predefinito . . . . . . . . . : 192.168.1.1
Server DHCP . . . . . . . . . . . . . : 192.168.1.1
IAID DHCPv6 . . . . . . . . . . . :
DUID Client DHCPv6. . . . . . . . :
Server DNS . . . . . . . . . . . . . : 192.168.1.1
NetBIOS su TCP/IP . . . . . . . . . . : Attivato

Scheda Ethernet Connessione di rete Bluetooth:

Stato supporto. . . . . . . . . . . . : Supporto disconnesso
Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
Indirizzo fisico. . . . . . . . . . . :
DHCP abilitato. . . . . . . . . . . . : Sì
Configurazione automatica abilitata : Sì

Scheda Tunnel isatap.Home:

Stato supporto. . . . . . . . . . . . : Supporto disconnesso
Suffisso DNS specifico per connessione: Home
Descrizione . . . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Indirizzo fisico. . . . . . . . . . . :
DHCP abilitato. . . . . . . . . . . . : No
Configurazione automatica abilitata : Sì

Scheda Tunnel Teredo Tunneling Pseudo-Interface:

Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Indirizzo fisico. . . . . . . . . . . :
DHCP abilitato. . . . . . . . . . . . : No
Configurazione automatica abilitata : Sì
Indirizzo IPv6 . . . . . . . . . . . . . . . . . : (Preferenziale)
Indirizzo IPv6 locale rispetto al collegamento . : (Preferenziale)
Gateway predefinito . . . . . . . . . : ::
IAID DHCPv6 . . . . . . . . . . . : 503316480
DUID Client DHCPv6. . . . . . . . :
NetBIOS su TCP/IP . . . . . . . . . . : Disattivato

C:\Users\ut>tracert 192.168.1.137

Traccia instradamento verso MediaBox-LX1.Home [192.168.1.137]
su un massimo di 30 punti di passaggio:

1 2 ms 3 ms 2 ms MediaBox-LX1.Home [192.168.1.137]

Traccia completata.

C:\Users\ut>tracert 192.168.1.137

Traccia instradamento verso MediaBox-LX1.Home [192.168.1.137]
su un massimo di 30 punti di passaggio:

1 PC.Win.Home [192.168.1.3] rapporti: Host di destinazione non raggiungibile.

Traccia completata.

C:\Users\ut>ipconfig /all

Configurazione IP di Windows

Nome host . . . . . . . . . . . . . . : PC.Win
Suffisso DNS primario . . . . . . . . :
Tipo nodo . . . . . . . . . . . . . . : Ibrido
Routing IP abilitato. . . . . . . . . : No
Proxy WINS abilitato . . . . . . . . : No
Elenco di ricerca suffissi DNS. . . . : Home

Scheda Ethernet Ethernet:

Suffisso DNS specifico per connessione: Home
Descrizione . . . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Indirizzo fisico. . . . . . . . . . . :
DHCP abilitato. . . . . . . . . . . . : Sì
Configurazione automatica abilitata : Sì
Indirizzo IPv6 locale rispetto al collegamento . : (Preferenziale)
Indirizzo IPv4. . . . . . . . . . . . : 192.168.1.3(Preferenziale)
Subnet mask . . . . . . . . . . . . . : 255.255.255.0
Lease ottenuto. . . . . . . . . . . . : venerdì 27 maggio 2016 13.17.12
Scadenza lease . . . . . . . . . . . : sabato 28 maggio 2016 13.17.12
Gateway predefinito . . . . . . . . . : 192.168.1.1
Server DHCP . . . . . . . . . . . . . : 192.168.1.1
IAID DHCPv6 . . . . . . . . . . . :
DUID Client DHCPv6. . . . . . . . :
Server DNS . . . . . . . . . . . . . : 192.168.1.1
NetBIOS su TCP/IP . . . . . . . . . . : Attivato

Scheda Ethernet Connessione di rete Bluetooth:

Stato supporto. . . . . . . . . . . . : Supporto disconnesso
Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
Indirizzo fisico. . . . . . . . . . . :
DHCP abilitato. . . . . . . . . . . . : Sì
Configurazione automatica abilitata : Sì

Scheda Tunnel isatap.Home:

Stato supporto. . . . . . . . . . . . : Supporto disconnesso
Suffisso DNS specifico per connessione: Home
Descrizione . . . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Indirizzo fisico. . . . . . . . . . . :
DHCP abilitato. . . . . . . . . . . . : No
Configurazione automatica abilitata : Sì

Scheda Tunnel Teredo Tunneling Pseudo-Interface:

Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Indirizzo fisico. . . . . . . . . . . :
DHCP abilitato. . . . . . . . . . . . : No
Configurazione automatica abilitata : Sì
Indirizzo IPv6 . . . . . . . . . . . . . . . . . : (Preferenziale)
Indirizzo IPv6 locale rispetto al collegamento . : (Preferenziale)
Gateway predefinito . . . . . . . . . : ::
IAID DHCPv6 . . . . . . . . . . . :
DUID Client DHCPv6. . . . . . . . :
NetBIOS su TCP/IP . . . . . . . . . . : Disattivato

C:\Users\ut>
Frakko
DD-WRT Guru


Joined: 06 May 2016
Posts: 521

PostPosted: Sat May 28, 2016 4:36    Post subject: Re: Problems with internal server to the network. Reply with quote
[quote="jwoods"][quote="Frakko"]>...
> You may also need to set up Port Range Forwarding.

It uses the 80,443,8001 doors.
How you configure the Port Range Forwarding?
Thank you.[/quote]

See this DD-WRT wiki article on Port Forwarding...

http://www.dd-wrt.com/wiki/index.php/Port_Forwarding

For example, my DIRECTV Genie STB uses ports 27177 and 27178.

You would need to find out from Mediabox what ports need to be forwarded.[/quote]

Excuse me you may also post you that proof request with the port forward and without port forward?


In Microsoft Windows ...

In a Command Prompt, run tracert 192.168.1.138 for Both wireless and ethernet and save the output for comparison.

Run ipconfig / all and save the output for comparison.

Start> Settings> Network & Internet ...

Check the property settings for the wireless and Ethernet adapters for difference.

Check to see if your wireless connection is September to Home or Work, and your Ethernet connection is September to Public.

Check if Network Discovery is turned off for the ethernet connection.

Check That All devices on the local network are in the same subnet (normally something like 255.255.255.0).

Thank you
Goto page Previous  1, 2, 3  Next Display posts from previous:    Page 2 of 3
Post new topic   Reply to topic    DD-WRT Forum Index -> Atheros WiSOC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum