Fatal Error

[phoenixsoap]

Just downloaded the app. Any type of connection I try and create is
met with a pop-up window proclaiming: "Fatal Error: nodename nor
servname provided, or not known".

Help! can't use this app at all because of this which is no fun
because it wasn't free.

[Jason]

I'm getting this exact same issue - unfortunately. Just bought it
today too..

[eric maland]

Hi,

Generally this error means that DNS resolution of the given hostname
has failed. Is there a way you can verify that the network you are
attached to has a DNS server that is properly resolving the hostname,
or that the hostname is typed correctly? Can you try another host and
see if that works?

It's almost-definitely DNS at play.

If you continue to have this problem let me know (pterm at
instantcocoa dot com) and I'll work with you in whatever way I can to
get it working for you.

Thanks!
Eric

[Joel]

Hi,

I am also receiving this error message today. It was working as of
last night, but not any more. I have verified the DNS is resolving
correctly and was able to access the same hostname via putty on my
pc. Please let me know if I can provide any further information.


Thanks,

Joel

[mrpunkin]

I noticed this error when I tried user@hostname as the host styntax.
Removing the user@ and letting the prompts handle it after DNS
resolving fixed my issues.

[Joel]

I was just about to post the same thing :)

Removed <user>@ and is working perfectly now.

> > > > > because it wasn't free.- Hide quoted text -
>
> - Show quoted text -

[hide]

Hi Eric,

I too am getting this error message.

I had Wifi enabled, turned it off to be on 3G, then attempted to
connect. I then opened another application that used network
(Twitterrific in this case), which connected, then went back into
pTerm and it connected as expected.

It seems that pTerm is holding onto a DNS setting for some reason.

Hope this helps.

~Shawn

[Geoff]

i had success with this trick as well. DNS resolution was failing
until I opened a page in safari, then i was able to log in
successfully.

[eric maland]

That's very interesting! I'll look into how PuTTY is doing name
service and see if it is somehow unreliable on iPhone OS. I've had a
number of reports of this.

[auralvance]

Same problem here, and opening up safari to a page fixed it as well.

Just to give a little more detail, it's definitely some sort of
internal caching because the issue happened immediately after I
switched back to radio (3G) from using my local wireless. Before
wireless it worked fine, on wireless it worked fine, then switching
back to 3G caused the choke... it refused to start any connections and
posted the same error as above. This leads me to believe it's still
using whatever cache it got from the wireless connection. Note:
restarting the phone did not solve the issue, only loading a new page
in safari did.

[Jason]

Hi,

I know this is a little late (been really busy), but on my home wi-fi
network I logged into a server of mine without any probs.

So I guess I can chalk it up to DNS.

Thanks,

- jason