unable to resolve host by name: (11001)

[Michael Mitschke]

Ok,
sorry for my missing answers the last days [i was sick]

so know my detail-explenation of this problem:

First of all: it all worked fine with the old vnc 3.x and tight vnc
versions!
So the file itself is fine!
I can use it with the other versions! The saved connections where made with
the old vnc but it dosnt work with a new creation with realvnc4 either!
->Since i had to use realvnc4 i get this 11001 error !!!
and i make the connections on the same machine i want to run them from!
I cant use an direct IP cause i have to use a dyndns!

sincerly
michael

-----Urspr|ngliche Nachricht-----
Von: Steve Bostedor [SMTP:***@tshore.com]
Gesendet am: Dienstag, 1. Februar 2005 16:07
An: Michael Mitschke; VNC
Betreff: RE: unable to resolve host by name: (11001)

Try editing the .vnc file to replace the host name with the IP address.
If this works, then you are having a name resolution problem that
doesn't involve VNC. You say that you can connect manually but do you
type the same text in the manual connect box that you see in the .vnc
file for the host name?

For example, you could be typing computer1 but the .vnc file has
computer1.vncscan.com as the hostname.

- Steve Bostedor
http://www.vncscan.com



-----Original Message-----
From: vnc-list-***@realvnc.com [mailto:vnc-list-***@realvnc.com] On
Behalf Of Michael Mitschke
Sent: Tuesday, February 01, 2005 6:13 AM
To: 'VNC'
Subject: AW: unable to resolve host by name: (11001)

Hi,
I dont have any problems to connect manually!

"How are you using the saved connections with vncviewer? Are you
double-clicking them"

^^right
no special tweaks or command lines

-----Urspr|ngliche Nachricht-----
Von: James Weatherall [SMTP:***@realvnc.com]
Gesendet am: Dienstag, 1. Februar 2005 11:42
An: 'Michael Mitschke'; 'VNC'
Betreff: RE: unable to resolve host by name: (11001)

Michael,

Do the connections work from the problem machine if you make them
normally, using the Connection dialog?

How are you using the saved connections with vncviewer? Are you
double-clicking them, running vncviewer with the -config command-line
option, etc?

-----Original Message-----
Sent: 01 February 2005 08:16
To: 'VNC'
Subject: unable to resolve host by name: (11001)
Hi,
(11001)] when i try to use my saved connections!
I already searched the list but couldnt find a resolution for this
problem....
_______________________________________________
VNC-List mailing list
http://www.realvnc.com/mailman/listinfo/vnc-list

[Gearry Judkins]

I apologize for starting a new thread, but I just subscribed to the list.

I am also having this error, running VNC 4.0 on Win2k. I created a .vnc
file and specified the host, and opened it by double-clicking on the file.
If I type the same host name into the client I connect with no problems.
The .vnc file was created on this machine, with the same software version.
If any more info would be helpful, I would be glad to provide it.

Gearry Judkins
FCHN Information Systems

[William Hooper]

Post by Gearry Judkins
I apologize for starting a new thread, but I just subscribed to the list.
I am also having this error, running VNC 4.0 on Win2k. I created a .vnc
file and specified the host,

How did you create the file?

Post by Gearry Judkins
and opened it by double-clicking on the file.

What command do you have associated with .vnc files?

[Gearry Judkins]

OK, only dorks reply to their own thread.

I thought I should add that I did further testing.

If I supply the IP in the .vnc file it still does not work. Perhaps I am
misunderstanding the purpose of the Host line, but I don't think so.

Gearry

[James Weatherall]

Gearry,

Check that however you are opening the .vnc file, the vncviewer command-line
used is of the form:

vncviewer -config <filename>

The form vncviewer <filename> will only work if <filename> contains
backslashes, so the above form is generally safer.

Regards,

Post by Michael Mitschke
-----Original Message-----
Sent: 07 February 2005 20:28
Subject: RE: unable to resolve host by name: (11001)
OK, only dorks reply to their own thread.
I thought I should add that I did further testing.
If I supply the IP in the .vnc file it still does not work.
Perhaps I am
misunderstanding the purpose of the Host line, but I don't think so.
Gearry
_______________________________________________
VNC-List mailing list
http://www.realvnc.com/mailman/listinfo/vnc-list

[Gearry Judkins]

Thanks, that was indeed the problem. I also discovered that this is much
easier to set up if you run the combined installer (to register the file
types, as is noted in the documentation), rather than just get the viewer
and go through registering the type yourself. I did RTFM, but was not
getting everything correct. I will blame it on Window's kludgy interface
for configuring file type handlers (one interface for folder customizations,
and another for global settings, and they almost look the same, at least on
2k). Yes, that makes me feel better.

Gearry

[Gearry Judkins]

I fixed the problem by downloading the full install of VNC, not just the
viewer, and only installed the viewer, custom install. This registered the
.vnc file type properly with windows, so that when I double-clicked on .vnc
files (or opened them via a browser) vncviewer was passed the -config option
to open the file. That solved my problem. Merely associating .vnc files
with vncviewer is not enough.

I am working on designing a web front end for connecting to multiple VNC
servers, using .vnc config files and the native viewer, although it could be
adapted to use the java viewer. My ambition is to build a web front end to
a database for managing multiple vnc hosts. Perhaps I am duplicating
something in the professional versions available, but it is a tool I need,
and I have some time but little $$$. I am sure other people have done
similar things, so perhaps people have ideas (or code) to share.

Gearry

-----Original Message-----
From: ***@quoka.com
To: 'Gearry Judkins'
Cc: vnc-***@realvnc.com
Sent: 2/8/2005 10:24 AM
Subject: AW: unable to resolve host by name: (11001)

did i miss something?
what was the solution for "our" problem?

-----Urspr|ngliche Nachricht-----
Von: Gearry Judkins [SMTP:***@fchn.org]
Gesendet am: Dienstag, 8. Februar 2005 15:29
An: 'James Weatherall'; Gearry Judkins; vnc-***@realvnc.com
Betreff: RE: unable to resolve host by name: (11001)

Thanks, that was indeed the problem. I also discovered that this is
much
easier to set up if you run the combined installer (to register the file
types, as is noted in the documentation), rather than just get the
viewer
and go through registering the type yourself. I did RTFM, but was not
getting everything correct. I will blame it on Window's kludgy
interface
for configuring file type handlers (one interface for folder
customizations,
and another for global settings, and they almost look the same, at least
on
2k). Yes, that makes me feel better.

Gearry

[Michael Mitschke]

well

but i have the "full" version running and it dosnt work either!
tomorrow i try to re-install the whole thing and than have a look how it
runs...

Mit Freundlichen Gr|ssen
Michael Mitschke

Quoka AG
-Helpdesk||Netzwerkservice-
Chemiestra_e 14-15
68623 Lampertheim
Tel. 06206 - 931 126

----- Originalnachricht -----
Von: Gearry Judkins <***@fchn.org>
Datum: Dienstag, Februar 8, 2005 5:23 pm
Betreff: RE: unable to resolve host by name: (11001)

Post by Gearry Judkins
I fixed the problem by downloading the full install of VNC, not
just the
viewer, and only installed the viewer, custom install. This
registered the
.vnc file type properly with windows, so that when I double-
clicked on .vnc
files (or opened them via a browser) vncviewer was passed the -
config option
to open the file. That solved my problem. Merely associating
.vnc files
with vncviewer is not enough.
I am working on designing a web front end for connecting to
multiple VNC
servers, using .vnc config files and the native viewer, although
it could be
adapted to use the java viewer. My ambition is to build a web
front end to
a database for managing multiple vnc hosts. Perhaps I am duplicating
something in the professional versions available, but it is a tool
I need,
and I have some time but little $$$. I am sure other people have done
similar things, so perhaps people have ideas (or code) to share.
Gearry
-----Original Message-----
To: 'Gearry Judkins'
Sent: 2/8/2005 10:24 AM
Subject: AW: unable to resolve host by name: (11001)
did i miss something?
what was the solution for "our" problem?
-----Urspr|ngliche Nachricht-----
Gesendet am: Dienstag, 8. Februar 2005 15:29
Betreff: RE: unable to resolve host by name: (11001)
Thanks, that was indeed the problem. I also discovered that this is
much
easier to set up if you run the combined installer (to register
the file
types, as is noted in the documentation), rather than just get the
viewer
and go through registering the type yourself. I did RTFM, but was not
getting everything correct. I will blame it on Window's kludgy
interface
for configuring file type handlers (one interface for folder
customizations,
and another for global settings, and they almost look the same, at
leaston
2k). Yes, that makes me feel better.
Gearry
_______________________________________________
VNC-List mailing list
http://www.realvnc.com/mailman/listinfo/vnc-list

[James Weatherall]

Michael,

No need to reinstall - just check the file association for .vnc files
(Tools->Folder Options->File Types from any Explorer window) and make sure
that the command-line for Opening those files looks something like:

"C:\program files\RealVNC\VNC4\vncviewer.exe" -config "%1"

i.e. the path to vncviewer.exe on your system, followed by the -config and
"%1" options.

Cheers,

Wez @ RealVNC Ltd.


-----Original Message-----
From: vnc-list-***@realvnc.com [mailto:vnc-list-***@realvnc.com] On
Behalf Of Michael Mitschke
Sent: 08 February 2005 16:49
To: Gearry Judkins; vnc-***@realvnc.com
Subject: Re: RE: unable to resolve host by name: (11001)


well

but i have the "full" version running and it dosnt work either! tomorrow i
try to re-install the whole thing and than have a look how it runs...

Mit Freundlichen Gr|ssen
Michael Mitschke

Quoka AG
-Helpdesk||Netzwerkservice-
Chemiestra_e 14-15
68623 Lampertheim
Tel. 06206 - 931 126

----- Originalnachricht -----
Von: Gearry Judkins <***@fchn.org>
Datum: Dienstag, Februar 8, 2005 5:23 pm
Betreff: RE: unable to resolve host by name: (11001)

Post by Gearry Judkins
I fixed the problem by downloading the full install of VNC, not
just the
viewer, and only installed the viewer, custom install. This
registered the
.vnc file type properly with windows, so that when I double-
clicked on .vnc
files (or opened them via a browser) vncviewer was passed the -
config option
to open the file. That solved my problem. Merely associating
.vnc files
with vncviewer is not enough.
I am working on designing a web front end for connecting to
multiple VNC
servers, using .vnc config files and the native viewer, although
it could be
adapted to use the java viewer. My ambition is to build a web
front end to
a database for managing multiple vnc hosts. Perhaps I am duplicating
something in the professional versions available, but it is a tool
I need,
and I have some time but little $$$. I am sure other people have done
similar things, so perhaps people have ideas (or code) to share.
Gearry
-----Original Message-----
To: 'Gearry Judkins'
Sent: 2/8/2005 10:24 AM
Subject: AW: unable to resolve host by name: (11001)
did i miss something?
what was the solution for "our" problem?
-----Urspr|ngliche Nachricht-----
Gesendet am: Dienstag, 8. Februar 2005 15:29
Betreff: RE: unable to resolve host by name: (11001)
Thanks, that was indeed the problem. I also discovered that this is
much easier to set up if you run the combined installer (to register
the file
types, as is noted in the documentation), rather than just get the
viewer
and go through registering the type yourself. I did RTFM, but was not
getting everything correct. I will blame it on Window's kludgy
interface
for configuring file type handlers (one interface for folder
customizations,
and another for global settings, and they almost look the same, at
leaston
2k). Yes, that makes me feel better.
Gearry
_______________________________________________
VNC-List mailing list
http://www.realvnc.com/mailman/listinfo/vnc-list

[Michael Mitschke]

thanks...

after the change i had the error: bad Name/Value pair
but i just had to re-create the connection files and now it works fine.

thanks to all


-----Urspr|ngliche Nachricht-----
Von: vnc-list-***@realvnc.com [mailto:vnc-list-***@realvnc.com]Im
Auftrag von James Weatherall
Gesendet: Dienstag, 8. Februar 2005 18:35
An: 'Michael Mitschke'; 'Gearry Judkins'; vnc-***@realvnc.com
Betreff: RE: RE: unable to resolve host by name: (11001)


Michael,

No need to reinstall - just check the file association for .vnc files
(Tools->Folder Options->File Types from any Explorer window) and make sure
that the command-line for Opening those files looks something like:

"C:\program files\RealVNC\VNC4\vncviewer.exe" -config "%1"

i.e. the path to vncviewer.exe on your system, followed by the -config and
"%1" options.

Cheers,

Wez @ RealVNC Ltd.


-----Original Message-----
From: vnc-list-***@realvnc.com [mailto:vnc-list-***@realvnc.com] On
Behalf Of Michael Mitschke
Sent: 08 February 2005 16:49
To: Gearry Judkins; vnc-***@realvnc.com
Subject: Re: RE: unable to resolve host by name: (11001)


well

but i have the "full" version running and it dosnt work either! tomorrow i
try to re-install the whole thing and than have a look how it runs...

Mit Freundlichen Gr|ssen
Michael Mitschke

Quoka AG
-Helpdesk||Netzwerkservice-
Chemiestra_e 14-15
68623 Lampertheim
Tel. 06206 - 931 126

----- Originalnachricht -----
Von: Gearry Judkins <***@fchn.org>
Datum: Dienstag, Februar 8, 2005 5:23 pm
Betreff: RE: unable to resolve host by name: (11001)

Post by Gearry Judkins
I fixed the problem by downloading the full install of VNC, not
just the
viewer, and only installed the viewer, custom install. This
registered the
.vnc file type properly with windows, so that when I double-
clicked on .vnc
files (or opened them via a browser) vncviewer was passed the -
config option
to open the file. That solved my problem. Merely associating
.vnc files
with vncviewer is not enough.
I am working on designing a web front end for connecting to
multiple VNC
servers, using .vnc config files and the native viewer, although
it could be
adapted to use the java viewer. My ambition is to build a web
front end to
a database for managing multiple vnc hosts. Perhaps I am duplicating
something in the professional versions available, but it is a tool
I need,
and I have some time but little $$$. I am sure other people have done
similar things, so perhaps people have ideas (or code) to share.
Gearry
-----Original Message-----
To: 'Gearry Judkins'
Sent: 2/8/2005 10:24 AM
Subject: AW: unable to resolve host by name: (11001)
did i miss something?
what was the solution for "our" problem?
-----Urspr|ngliche Nachricht-----
Gesendet am: Dienstag, 8. Februar 2005 15:29
Betreff: RE: unable to resolve host by name: (11001)
Thanks, that was indeed the problem. I also discovered that this is
much easier to set up if you run the combined installer (to register
the file
types, as is noted in the documentation), rather than just get the
viewer
and go through registering the type yourself. I did RTFM, but was not
getting everything correct. I will blame it on Window's kludgy
interface
for configuring file type handlers (one interface for folder
customizations,
and another for global settings, and they almost look the same, at
leaston
2k). Yes, that makes me feel better.
Gearry
_______________________________________________
VNC-List mailing list
http://www.realvnc.com/mailman/listinfo/vnc-list