PuTTY and WinSCP fail but xFx shows activity
Have I missed soemthing...... I've recently set up a HAHub(HAH9) as a clone of my fully working home system Hub(HAH1), and put it onto a remote LAN.... I've tried to remotely access HAH9 and can't get onto it, so I'm using LogMeIn to access a PC on the remote LAN and try and play with HAH9 'locally' - but PuTTy opens up, shows a cursor and halts with no login, whereas WinSCP will open up, Say 'Searching for Host' then 'Connecting to Host' then error out with 'Host not communicating' and I have to abort out... xFx viewer works fine and shows that HAH9 is active but the Pachube instance only refreshes every 2.5 mins not 60 seconds like all the others...CurrentCost ch1, 2 and 3 and total and temp are all picking up data correctly, but nothing is getting through to Pachube!
Any ideas, please!!!
I could be a long shot, but have you check you've enabled SSH through the web GUI?
Karl
Without a valid timestamp on your box SSL will fail. Its a requirement that clocks be no more than 2-3min out otherwise SSL will fail. Enable telnet that will get you in.
If the clock isnt' synching the you have a DNS lookup issue on the livebox.
UPDATE: Also make sure that the NTP host that is configured is a valid NTP time source and that you can resolve this hostname once you have TELNET access on your box enabled.
See the screenshot -> http://www.dbzoo.com/livebox/webserver#network_services
Brett
Putty has a TELNET option just do you what you normally do but change the RADIO button selection and enable TELNET as a service on the web gui which you said is working.
Once on the livebox use
# nslookup <host>
See telnet using putty screenshot below.
Are both the gateway and DNS set correctly in the web interface. You could also try changing the DNS to an external server and not your local router. Reboot if you change these.
Karl
Did you recently upgrade your cable modem/router? As this would mean that its no longer acting as a DNS proxy. I think virgin's new super duper cable modem does this as I noticed that when Derek got his new one DNS things started breaking too. As instead of proxying via the cable modem now it prefers to pass along the external DNS server IP's.
Karl was on the money thou, set the DNS IP to be the external IP addresses instead. That should be enough. Telnet is handy which is why I've not removed this service, and why I indeed have it :)
Brett
Sounds like you have duplicate MAC address issue. Did you adjust this for your 2nd unit? A UDP broadcast will work regardless of this issue (even if its very bad condition) everthing else that uses TCP will just bomb.
Brett