[19. April 2013] A-400 Advanced Network Setup now available | [11 Jan. 2013] Customize your A-400 Home Screen

Firmware: A-400 [13 May 2013] | C-300 [30 Nov. 2012] | A-300 [30 Nov. 2012] | C-200 [21 Jan. 2013] | A-200/A-210 [10 Aug. 2012]

Just got your NMT | WIKI has the answers | Search the forum | Forum Rules/Policy | Firmware & Official NMT News | Popcornhour manuals



User(s) browsing this thread: 1 Guest(s)
Thread Closed 
My little annoyance
07-29-2010, 01:25 PM
Post: #16
RE: My little annoyance
are you using a static ip (information entered into your pch) or a reserved/static dhcp setting? I actually recommend the later which is done in your routers dhcp setup so the pch always gets the same ip but as dns servers change it gets updated..

This might fix your issue if dhcp worked.
Find all posts by this user
07-29-2010, 07:28 PM
Post: #17
RE: My little annoyance
(07-29-2010 01:25 PM)accident Wrote:  are you using a static ip (information entered into your pch) or a reserved/static dhcp setting? I actually recommend the later which is done in your routers dhcp setup so the pch always gets the same ip but as dns servers change it gets updated..

This might fix your issue if dhcp worked.

Yes, I was running a dynamic ip as of yesterday, for testing. And it does work, but instead I can't access the shell on the pch confused And what causes that I seriously have no clue.
Find all posts by this user
07-29-2010, 08:04 PM
Post: #18
RE: My little annoyance
well if your using dhcp, what IP are you trying to connect with for telnet? You will have to look on the pch or your dhcp server to see what IP it got.
Find all posts by this user
07-30-2010, 03:49 PM
Post: #19
RE: My little annoyance
(07-29-2010 08:04 PM)johnpoz Wrote:  well if your using dhcp, what IP are you trying to connect with for telnet? You will have to look on the pch or your dhcp server to see what IP it got.

Of course, I know. But it still won't let me in Smile
Find all posts by this user
07-30-2010, 04:12 PM
Post: #20
RE: My little annoyance
Well that makes no sense what so ever since being dhcp or static has NOTHING to do with the telnet server running. Possible you are running a software firewall on your machine that blocks access outbound telnet to this new IP. Its possible you had setup up an allow on your firewall to static, but now its different so your firewall is blocking?

You will notice that the telnetd binds to ALL IPs on the pch

netstat -an
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 0.0.0.0:2020 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:9999 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:8883 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:6357 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:23 0.0.0.0:* LISTEN

So its not like telnet would of been setup to be bound to only your static IP that is no longer valid. If I had to guess I would suggest you double check any software firewall your running on your computer, or antivirus suite -- since lots of them come with firewalls now.
Find all posts by this user
07-30-2010, 05:01 PM
Post: #21
RE: My little annoyance
(07-30-2010 04:12 PM)johnpoz Wrote:  Well that makes no sense what so ever since being dhcp or static has NOTHING to do with the telnet server running. Possible you are running a software firewall on your machine that blocks access outbound telnet to this new IP. Its possible you had setup up an allow on your firewall to static, but now its different so your firewall is blocking?

You will notice that the telnetd binds to ALL IPs on the pch

netstat -an
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 0.0.0.0:2020 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:9999 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:8883 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:6357 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:23 0.0.0.0:* LISTEN

So its not like telnet would of been setup to be bound to only your static IP that is no longer valid. If I had to guess I would suggest you double check any software firewall your running on your computer, or antivirus suite -- since lots of them come with firewalls now.

No, I don't use a firewall, or any antivirus software.
Something is off, since I can connect through telnet just when the popcorn has finsished booting, and I lose connection after a minute or so.
Of course, logic dictates that static och dynamic ip has nothing to do with it, but something does change when changing the ip properties.. and I have no clue on what can cause something like that, it shouldn't make any difference.
Find all posts by this user
07-30-2010, 05:07 PM
Post: #22
RE: My little annoyance
Well I thought you were having issues with telnet stopping even when on static?

You might want to install dropbear (ssh) and try that vs telnet. But yeah it makes no sense unless the process is stopping for some reason??
Find all posts by this user
07-30-2010, 05:32 PM
Post: #23
RE: My little annoyance
(07-30-2010 05:07 PM)johnpoz Wrote:  Well I thought you were having issues with telnet stopping even when on static?

You might want to install dropbear (ssh) and try that vs telnet. But yeah it makes no sense unless the process is stopping for some reason??

Ah, didn't know there was a ssh daemon as well. I actually can connect through that, but I haven't figured out how the autenthification works, but I can at least connect.
Find all posts by this user
Thread Closed 


Forum Jump: