Amahi Forums

Hello,

First thanks to all the Amahi team. It's great to have something that is making Unix/Fedora easier.
But I must admit that i'm pretty new to all that and I feel like I have a dying pinguin in the a*s.

I setup Amahi on my old Athlon64, erasing windows from it as I wanted to have something lighter.
And lighter than WHS to do what I wanted this server to do (files sharing, external download machine, ftp, media serving etc...).
The system is fully working now. I struggled a bit with the configuration of the VNC, the domain controller, the file sharing. But all those are OK by now on my system.
I can reach the Internet from the Amahi machine.

I use it headless but still need sometime to VNC for some stuff.

The domain name is 'home.com', I didn't changed it.

From my remote (main) Pc under XP pro, I succeed in reaching "http://hda", the setup, the applications installation page (I struggled a bit with that one).
BUT I can't reach any installed application from the Dashboard.
Like "http://tflux.home.com/" or "http://transmission.home.com/" the two and only apps installed.
It kick me to a 'home.com' domain over the internet. Any other attempts (with wrong names) leads to a 'http://guide.opendns.com' page.

Help me unstuck this pinguin from my A*S please

Ps: Sorry for the average English

your english is fine

hmmm, we have seen this (that even with the full domain, you cannot get to the app) in a couple of instances recently.

it could be a bug or updates or something on our side ... the first thing is to see if it's a server problem or a client problem.

can you reach "http://tflux.home.com/" in the server?

can you ping tflux.home.com in the client and get the IP of your hda?

in the server, does this show anything:

Thanks for the reply and the help on the IRC.

I can reach "http://tflux.home.com/" in the server.

But doing a ping on tflux.home.com from the client give me an external IP.

I can't do the command because, I don't know why, my vnc isn't working, I got a black screen.
I'm not on site and can't reboot the server.
Is there a way to stop and relaunch the vnc remotly?

If not I'll try it as soon as I'm back home (several days).

Julien

EDIT: Another strange behavior is that when I try to reach one of my app (tflux, transmission or webvnc), I'm sent to some "http://guide.opendns.com" webpage. It's a feature from Amahi, isn't it?

Thanks for the reply and the help on the IRC.

I can reach "http://tflux.home.com/" in the server.

But doing a ping on tflux.home.com from the client give me an external IP.

I can't do the command because, I don't know why, my vnc isn't working, I got a black screen.
I'm not on site and can't reboot the server.
Is there a way to stop and relaunch the vnc remotly?

If not I'll try it as soon as I'm back home (several days).

Julien

EDIT: Another strange behavior is that when I try to reach one of my app (tflux, transmission or webvnc), I'm sent to some "http://guide.opendns.com" webpage. It's a feature from Amahi, isn't it?

Just out of curiosity have tried the steps listed on this link? if you have my apologies.

http://wiki.amahi.org/index.php/Network_Troubleshooting

Also what edition of Fedora did you install?

I installed the Fedora-10-x86_64-DVD iso.

I've done the test and the 'ping router' from the XP client machine is the only thing that doesn't work.

I haven't done the ping on the amahi server because of my VNC and its black screen.
I'll try and see more later tomorow and will tell you what's going on.

Update here.

I simply applied the 26 updates on the amahi machine and everything is working now.
I gained access to the apps of my dashboard.

I still can't ping 'router' (not 'server', my bad) from any machine but as everything's working I don't mind.

why would you want to ping "server" unless you have something on your network called "server".
amahi's default is "hda" or "hda.home.com". If you get a reply from that, then the hda is on the network.
there are some issues with the dns resolution of some apps etc but most work.

In fact I ping'd the router (sorry it was late at night when I answered) simply because it's on the "Network troubleshouting" document.
Some people here asked me to do those test and since it's the only thing that is not working I put it here

But, as I said, my problem is solved by applying the 26 pending updates.
I ping'd hda from my remote XP computer, the hda was responding but I had no apps running thru the dashboard at that time. Now it's fine.

thanks
julien

I had this problem, but found that the problem was the setup of the network connections on the client PCs.

You must set them to get their IP by DHCP AND their DNS as well. Otherwise the client PC will search the internet BEFORE it searches the local network.

(I know, because I wsa there...)

But, as I said, my problem is solved by applying the 26 pending updates.

How did you apply those updates?

I have tried http://wiki.amahi.org/index.php/Linux-hda_commands

and the amahi updates:

rpm -Uvh http://dl.getdropbox.com/u/364883/Amahi ... noarch.rpm = updates HDA

and it just display the error - url not found - transfer failed...