I have a problem with tightvnc, when I set up a dinamic ip with networkmanager it works fine but if I set up a static address connection it display an error
“You have been unexpectedly disconnected from ‘hometsa-comp’. Would you like to reconnect?”
“Couldn’t convert ‘hometsa-comp’ to host address”
I have setup the ip address, netmask, gateway and dns server in the network manager static address, it works when I setup the vnc connection using ip address instead of hostnames.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Perhaps DDNS is in use. Does your client machien have ‘hometsa-comp’ in
its /etc/hosts (or equivalent) file so it can resolve that name to an IP
address? Does connecting via IP address work when the IP is static (vs.
connecting via hostname)? Does your DNS server on your network (if
applicable) resolve to your machine properly?
dig @dnsServerIPAddressHere hometsa-comp
Test the above (with your IP address in the first spot after the ‘@’ sign)
when using dynamic and static IPs to see a difference.
Good luck.
On 10/12/2010 04:36 PM, Easgs wrote:
>
> I have a problem with tightvnc, when I set up a dinamic ip with
> networkmanager it works fine but if I set up a static address connection
> it display an error
>
> “You have been unexpectedly disconnected from ‘hometsa-comp’. Would
> you like to reconnect?”
>
> “Couldn’t convert ‘hometsa-comp’ to host address”
>
> I have setup the ip address, netmask, gateway and dns server in the
> network manager static address, it works when I setup the vnc connection
> using ip address instead of hostnames.
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJMtOSKAAoJEF+XTK08PnB5cf0P/2XwKOV+fyhZRaN4dhp85erE
xVloieWya5vgAf8ewugU7SSjJq5AdElqR8MUBThf9zFe5XL5yzLUUFAvPTh7Q85/
WUSot9uA5JhPm5S9Ysdms8NyS60JejJQOwhJbTLsX7CTRmVe9PzZ/BJHiK3hc7Jn
qkI2NY0dIEDXi5g7l671DfxK56g0fQbHAL/rLvzUMyl6GlUk1JoMCA/FpK0m5H8g
3dl4JY5jXQvV7GPTTlvv6GxfhVGg4zkmIXOyRprfBRwyeEoSrsHSTk/6f/PJHPa4
abkcH5aqh13evvjCtmEOlmuKd1CFmU2stdyIUY+gPWo28KMMu8nyPLcnWAC5kfpj
SZ0K1ARkr3D8PdC0P7HoZKOVBgOVWQYTyK3bKfktF7W4B+UC1xkpuWcEzFPENJFD
vrnFAympmiUPlb3E/HRWJly+QVscd0qRS3yIqaz/8GLYGWLRZBbW6AH9+m5Bwwq6
HN0I4pCT80RfsMlS1zBNpyANqQVGcz22DwspdVgIcZqhdftCPfGEnJsbVz5Nopen
SbodYnz3MrVY0CjM4WN0SEpNfqQMZ+SR0pViGo4L7hRb4EOHRxQiN/HuSL5umVZP
NsI/CEH7RVWVSU+LqkdxUdgInKmFIpgZV/eT3ShvLMLAKAkCKVg6sRHY9lLep5Jt
qryJ6KOBaMRHAhBznseo
=LP8S
-----END PGP SIGNATURE-----
perhaps DDNS is in use. Does your client machien have ‘hometsa-comp’ in
its /etc/hosts (or equivalent) file so it can resolve that name to an IP
address?
no it doesn’t
Does connecting via IP address work when the IP is static (vs.
connecting via hostname)?
yes it does, when the ip is static it only works with IPs instead of hostnames
Does your DNS server on your network (if
applicable) resolve to your machine properly? it is a Windows domain, the domain controller is a 2003 server and all clients are windows xp, only this pc is an opensuse 11.3 32 bits box
dig @dnsServerIPAddressHere hometsa-comp
Test the above (with your IP address in the first spot after the ‘@’ sign)
when using dynamic and static IPs to see a difference.
it is my pc ip address or the dns server address?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
In waiting why not try both and see which one works?
If your DNS server’s IP was 192.1.1.1 the command would be the following:
dig @192.1.1.1 hometsa-comp
Post the output which will probably be something like the following:
; <<>> DiG 9.7.1 <<>> @192.1.1.1 hometsa-comp
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 12405
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;hometsa-comp. IN A
;; AUTHORITY SECTION:
… 10800 IN SOA a.root-servers.net.
nstld.verisign-grs.com. 2010101300 1800 900 604800 86400
;; Query time: 25 msec
;; SERVER: 192.1.1.1#53(192.1.1.1)
;; WHEN: Wed Oct 13 09:48:41 2010
;; MSG SIZE rcvd: 105
Good luck.
On 10/13/2010 08:36 AM, Easgs wrote:
>
> perhaps DDNS is in use. Does your client machien have ‘hometsa-comp’ in
> its /etc/hosts (or equivalent) file so it can resolve that name to an
> IP
> address?
>
> no it doesn’t
>
>
> Does connecting via IP address work when the IP is static (vs.
> connecting via hostname)?
>
> yes it does, when the ip is static it only works with IPs instead of
> hostnames
>
> Does your DNS server on your network (if
> applicable) resolve to your machine properly? it is a Windows domain,
> the domain controller is a 2003 server and all clients are windows xp,
> only this pc is an opensuse 11.3 32 bits box
>
>
>> dig @dnsServerIPAddressHere hometsa-comp
>>
>> Test the above (with your IP address in the first spot after the ‘@’
>> sign)
>> when using dynamic and static IPs to see a difference.
>
> it is my pc ip address or the dns server address?
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJMtdULAAoJEF+XTK08PnB5g/kQALexT5u8JPw/aSG8dWf6GuBL
caiP7U8dY4jVYG9AIAEbBq7XIilKDX5X+TyyuQWY56Ire/c5v/HDlIYTZR7NRG+P
q0xInQ+45w1uQpexfBzpd5wxpE7BfaPgwSEMuRXsHJQuq3L8kc1bdYSXjpgEUh4F
SsTGPzM0rWGKQKQ5/IDCXGj3YcKDwYVPEQLS/x4hnFSz5oaJVZnDYRv0+3lSn57P
Qer7Av70cx1olj3FEMSScI7AOT0Dn9dldyIdjPNXOCs4w0lc6I335qz8DjwSC+39
ClwLmziUszsPD3v4mlOGus3D6z6YSoqhKrJxkyigXAbetBXzAh9Yot4W+XCjRyc8
Tz46jaUckMtoAUBO3ICZi0vlM88kjrpv0tR2VE23vTRu/KhttEklagJ5fQJJ1NhL
f5BNALfEnxaLcaMmUQ9HrLTHsHPYI+i9Q1N6/uTIfD7diIt0zFMDKU7E9HLNz6/O
kmPgvHvpxWoz0DlgNhnpXcmlHMqNuZsFM0v2r62QY8IEGQaHT9jiBtUN0a1ww1Wg
Tg3RUDRcaiWAxYIqYVGsNyqK2IwpUfzl4+8uQrIxyFhYeJrReb6saKM+OZe1Dbp9
dZNyO99UDVo5Z0dD7l43uv49QWzpyv5u2wTc+TLpa0X3Q1/DwOv96cF4DxPN4Hrn
+fvmeh6YLdh+cwKVHnWb
=uDA/
-----END PGP SIGNATURE-----
with dinamic IP
easgs:/home/easgs # dig 192.168.0.2 hometsa-comp
; <<>> DiG 9.7.1 <<>> 192.168.0.2 hometsa-comp
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 54415
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;192.168.0.2. IN A
;; AUTHORITY SECTION:
. 10800 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2010101300 1800 900 604800 86400
;; Query time: 84 msec
;; SERVER: 192.168.0.2#53(192.168.0.2)
;; WHEN: Wed Oct 13 10:12:59 2010
;; MSG SIZE rcvd: 104
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 51021
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;hometsa-comp. IN A
;; Query time: 0 msec
;; SERVER: 192.168.0.2#53(192.168.0.2)
;; WHEN: Wed Oct 13 10:12:59 2010
;; MSG SIZE rcvd: 30
with static IP
easgs:/home/easgs # dig 192.168.0.2 hometsa-comp
; <<>> DiG 9.7.1 <<>> 192.168.0.2 hometsa-comp
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 30501
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0;; QUESTION SECTION:
;192.168.0.2. IN A;; AUTHORITY SECTION:
. 7871 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2010101300 1800 900 604800 786
;; Query time: 0 msec
;; SERVER: 192.168.0.2#53(192.168.0.2)
;; WHEN: Wed Oct 13 10:14:53 2010
;; MSG SIZE rcvd: 104
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 15611
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;hometsa-comp. IN A
;; Query time: 0 msec
;; SERVER: 192.168.0.2#53(192.168.0.2)
;; WHEN: Wed Oct 13 10:14:53 2010
;; MSG SIZE rcvd: 30
thanks for the help
Just something to take a look at…
I seem to remember when setting up a static address in YAST, I had to make modifications in <both> Network Devices and the Host file, ensuring both are consistent with each other. It’s easy to overlook or mis-configure one or the other.
Also, although it should not make a difference with modern versions of almost any OS I would generally do a reboot after changing from dynamic to static addressing or vice versa to be certain that the local dns resolver cache (and anything else) is cleared.
HTH,
Tony
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
No, you removed the ‘@’ sign and it needs to be there. See my previous post.
Good luck.
On 10/13/2010 10:36 AM, Easgs wrote:
>
> with dinamic IP
>
>> easgs:/home/easgs # dig 192.168.0.2 hometsa-comp
>>
>> ; <<>> DiG 9.7.1 <<>> 192.168.0.2 hometsa-comp
>> ;; global options: +cmd
>> ;; Got answer:
>> ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 54415
>> ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
>>
>> ;; QUESTION SECTION:
>> ;192.168.0.2. IN A
>>
>> ;; AUTHORITY SECTION:
>> . 10800 IN SOA a.root-servers.net.
>> nstld.verisign-grs.com. 2010101300 1800 900 604800 86400
>>
>> ;; Query time: 84 msec
>> ;; SERVER: 192.168.0.2#53(192.168.0.2)
>> ;; WHEN: Wed Oct 13 10:12:59 2010
>> ;; MSG SIZE rcvd: 104
>>
>> ;; Got answer:
>> ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 51021
>> ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
>>
>> ;; QUESTION SECTION:
>> ;hometsa-comp. IN A
>>
>> ;; Query time: 0 msec
>> ;; SERVER: 192.168.0.2#53(192.168.0.2)
>> ;; WHEN: Wed Oct 13 10:12:59 2010
>> ;; MSG SIZE rcvd: 30
>>
>
> with static IP
>
>> easgs:/home/easgs # dig 192.168.0.2 hometsa-comp
>>
>> ; <<>> DiG 9.7.1 <<>> 192.168.0.2 hometsa-comp
>> ;; global options: +cmd
>> ;; Got answer:
>> ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 30501
>> ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
>>
>>
>>
>> ;; QUESTION SECTION:
>>
>> ;192.168.0.2. IN A
>>
>>
>>
>> ;; AUTHORITY SECTION:
>>
>> . 7871 IN SOA a.root-servers.net.
>> nstld.verisign-grs.com. 2010101300 1800 900 604800 786
>>
>> ;; Query time: 0 msec
>> ;; SERVER: 192.168.0.2#53(192.168.0.2)
>> ;; WHEN: Wed Oct 13 10:14:53 2010
>> ;; MSG SIZE rcvd: 104
>>
>> ;; Got answer:
>> ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 15611
>> ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
>>
>> ;; QUESTION SECTION:
>> ;hometsa-comp. IN A
>>
>> ;; Query time: 0 msec
>> ;; SERVER: 192.168.0.2#53(192.168.0.2)
>> ;; WHEN: Wed Oct 13 10:14:53 2010
>> ;; MSG SIZE rcvd: 30
>>
>
> thanks for the help
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJMtenaAAoJEF+XTK08PnB5S4cP+gLIywuYxJK/k5mtK2lAuRMW
y+aO8t/B9siy+joCpL1AvNo+2h7wzPJslvTCOHaNBDZ9MJEmcQuoi3E0gLWJ5ziX
tsvzaKsDfu5on4wa/MHZrgGcjl7Is/rf/Mm2UxohpStr9rrz+b49G0ozSxboLb8A
ghh33cydLmW3Mb0Y0tVz5P9SvH9kYbCRoE7nMq8VCIqfNm9WHTcXek5YAeSQs2Yi
04hkRbzywNzZdhfgao24cd9KyGZhhD6Pr4uo2ACzBJoUJjLTfmR5L34lDgdUgo3k
32LGuFGjivz1MzlVP6Y0yWrP4zW7WKQmvWQYs3NdGniExkCMeMoMfe8aNrXS5KYE
tfG0yP4S+La0ujMX5RxjePKvy3CUhR9a3655JjFBiMjCQu/6MfrNGN3iR5E65ybu
uQ40Nu1VyXqAh8gjqJ5twa1Tbo2lcVAPAs5qLmgKce+8p8CvGy9BjLlBNOCz5IDa
CGq/wq1aXuv2gnpOIb9fZWIWdg569m/poVXSzGnWzNDR3TVPfjkkntxPfzEfPVfF
95KsamBW1te31rifu3iMLIE+pxoZ+RsXWGxfzsiggIIehJr9lUGSH6Xhz3ZY2EJ3
F520EOF1SeyOHUlnKedpzcqchcLUhczQmicoUEPzi9TuFamQ0JoBjEoivL9S3XnM
ORJVWk2MmgOIJEBgWqLT
=C/Z4
-----END PGP SIGNATURE-----
with static IP
easgs:/home/easgs # dig @192.168.0.2 hometsa-comp
; <<>> DiG 9.7.1 <<>> @192.168.0.2 hometsa-comp
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 760
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;hometsa-comp. IN A
;; Query time: 0 msec
;; SERVER: 192.168.0.2#53(192.168.0.2)
;; WHEN: Wed Oct 13 11:57:32 2010
;; MSG SIZE rcvd: 30
with dinamic IP
easgs:/home/eduardo # dig @192.168.0.2 hometsa-comp
; <<>> DiG 9.7.1 <<>> @192.168.0.2 hometsa-comp
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 14031
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;hometsa-comp. IN A
;; Query time: 0 msec
;; SERVER: 192.168.0.2#53(192.168.0.2)
;; WHEN: Wed Oct 13 11:59:19 2010
;; MSG SIZE rcvd: 30
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
So it would appear your DNS server knows nothing in either case, so that’s
interesting. With both static and dynamic try the following:
ping -c 1 hometsa-comp
Good luck.
On 10/13/2010 12:06 PM, Easgs wrote:
>
> with static IP
>
>> easgs:/home/easgs # dig @192.168.0.2 hometsa-comp
>>
>> ; <<>> DiG 9.7.1 <<>> @192.168.0.2 hometsa-comp
>> ; (1 server found)
>> ;; global options: +cmd
>> ;; Got answer:
>> ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 760
>> ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
>>
>> ;; QUESTION SECTION:
>> ;hometsa-comp. IN A
>>
>> ;; Query time: 0 msec
>> ;; SERVER: 192.168.0.2#53(192.168.0.2)
>> ;; WHEN: Wed Oct 13 11:57:32 2010
>> ;; MSG SIZE rcvd: 30
>>
>
>
> with dinamic IP
>
>> easgs:/home/eduardo # dig @192.168.0.2 hometsa-comp
>>
>> ; <<>> DiG 9.7.1 <<>> @192.168.0.2 hometsa-comp
>> ; (1 server found)
>> ;; global options: +cmd
>> ;; Got answer:
>> ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 14031
>> ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
>>
>> ;; QUESTION SECTION:
>> ;hometsa-comp. IN A
>>
>> ;; Query time: 0 msec
>> ;; SERVER: 192.168.0.2#53(192.168.0.2)
>> ;; WHEN: Wed Oct 13 11:59:19 2010
>> ;; MSG SIZE rcvd: 30
>>
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJMtftVAAoJEF+XTK08PnB5pREQAIHaQvlDAOPCKgIs/ALIYq3Z
omP4eQ4ksS70YhWRNkqgOJRurBqbSy9Cju8Lr3k2bSsqXZ8UQSXdhsrezmKDuYfR
M/clabLCeL7chplgrVwl/YZ7cx544CXvYsPnHS5qTv5uNwXAgKCMp/qRRX/SXxWp
t8lyGPTXYcLJLlI7Xadl5Fih1D4GsnDzRU+F/v0FGZ/cWrz9AgT5yq4f/JAoXf/s
4DRXpoNKXRZUNODQulTgXKcw/zqKGUVUfFLN6uf0Icfhw1tvlOwQE1XpJ6L2CDux
NbrUpvKnLoIAbzkBzTgG5gUfkvE/05CpWJApTI0AhdRitQyZ/h7SdF9FvRuFHq8R
f9r32q3E0nEfezR25ieHm63fIdekC64uJZNn46S4qLbpGuYSCYnBvPd0zHKzQZMW
Az2DB4i2Ezsj4CTdDxihzEEKsKoZ0dxBOEw4rz3ThW80fjz9iZ9LtBAs4g0/2QaC
eulFSEQZFgCsYbM85rvZoeuhg7ejrKBriqILZVtCa19kWbUjCKEf/vQxFyAL0une
I9lzrcB1QyDrAbOv1ZxEuCZNqto1yThZDErnMcYn2cmtrjr33Mq1xB2lfOVL7NO+
hi+V0WyAaly8RLC7WDqIAUQ7CUYL8eN4jVahZj6nuqh43nbXGtIJ52TbfJuj6UWg
5zVd2A6gC0RUYzwIeN/t
=QbZK
-----END PGP SIGNATURE-----
static IP
easgs:/home/easgs # ping -c 1 hometsa-comp
ping: unknown host hometsa-comp
dinamic
easgs:/home/easgs # ping -c 1 hometsa-comp
PING hometsa-comp.sienic.com.ni (192.168.0.141) 56(84) bytes of data.
64 bytes from hometsa-comp.sienic.com.ni (192.168.0.141): icmp_seq=1 ttl=128 time=0.980 ms
— hometsa-comp.sienic.com.ni ping statistics —
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.980/0.980/0.980/0.000 ms
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
So something on your system, when you do it dynamically, is able to find
the (presumably) remote system by name. If I didn’t know better I’d say
your /etc/hosts file was different between static and dynamic with that
entry in there while dynamic, but I do not understand how that would
happen unless it was in a config file somewhere. If this is happening
because of some network configuration (DHCP server giving out names
somehow, which is not something I think DHCP normally does) then a LAN
trace would show it. A LAN trace may be a good option in any case to see
if somehow the system is resolving the name via a server you are not
expecting when using a dynamic address. Just to confirm, you’re trying to
VNC to a remote machine, right? Something other than the box from which
you are connecting?
sudo /usr/sbin/tcpdump -n -s 0 -w /tmp/cap0.cap
#perform test in another terminal and then Ctrl+C this one when done
#and send the /tmp/cap0.cap file (or post it somewhere) for review.
Good luck.
On 10/13/2010 01:36 PM, Easgs wrote:
>
> static IP
>
>> easgs:/home/easgs # ping -c 1 hometsa-comp
>> ping: unknown host hometsa-comp
>>
>
>
> dinamic
>
>>
>>
>> easgs:/home/easgs # ping -c 1 hometsa-comp
>> PING hometsa-comp.sienic.com.ni (192.168.0.141) 56(84) bytes of data.
>> 64 bytes from hometsa-comp.sienic.com.ni (192.168.0.141): icmp_seq=1
>> ttl=128 time=0.980 ms
>>
>> — hometsa-comp.sienic.com.ni ping statistics —
>> 1 packets transmitted, 1 received, 0% packet loss, time 0ms
>> rtt min/avg/max/mdev = 0.980/0.980/0.980/0.000 ms
>>
>>
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJMthhbAAoJEF+XTK08PnB5OGMP/jBQsxvguE8aFp5RiXNVX3q9
7dp6D4xZ1hyn7OgOgzoKemObbL9nulSTf3uL6borfDhFkk0NQrvlkOB8G2bgPo+a
nkGiK9A/i2JfUdWRZ6OJRS3WayS20/s0e8vBm76+Saf+qgFGn9bn5lC7aSacoUBs
/39YymGOVrOvNINFw35V4/c6PVJYPus7yfcRRxC7n5iBNZyztOjI5Oe1HW0VVmFn
GHuIx4g7tPPRhZ58KvsJAPBM9IrRhl698pG/0fJ2g5Xwqo3Tu5fsWv2Kvqi8r6aT
Oz8MzhzwR2U2/qAvNLTWTH45IJP+/EuOfkibW8XL6yyWEWAAog3YwU6j1flIaT89
pOcPrCGASvIJ6zwZYh6I0PRVZPai/CnllVQmVfsM6bI6A2pOXiZDM9xyH9bXG4+j
YD8Fih9RXbNvAvK0sXc/8nCVoFVCOf7HrzB6VWaWHClWOUEzsqlNTvf5oSKY4G95
SAHCVIbtjaLyy67Ojz0LOGi9NIWoXK7rYRKLsb+8PjSchGvywn+GNQFsC3Bt+u1m
4IOt1PMmev8epYzSgP89YdPFrccSQPTnC+xz3HoTQjxC7ejoLAJMsDwUkLfM1Bd5
P7lbiXhfg9Yd2WRpNIVVhiYylDbI/sBvQtow3iqcUBvN73RlYYjIS7afjRWxwyHC
bSTwEJWZFTzL2i1A/xko
=uTS3
-----END PGP SIGNATURE-----
Just to confirm, you’re trying to VNC to a remote machine, right? yes
Something other than the box from which you are connecting? it doesn’t connect to any pc when using static IP, the problem is that there are several pc in the network and we use vnc to give remote support, all the pc are windows xp boxes.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
No, it does connect to things with a static IP. The problem as I
understand it and as you have described it is that your system does not
have a way to RESOLVE TO that static ip from the hostname but somehow it
does resolve to an IP address when using a dynamic IP. That normally
happens via DNS (but you said you’re not using DNS for the hostnames) or
else it happens via /etc/hosts files (which you are obviously not
manipulating on your own) so the next step is to figure out how it is
working with dynamic IPs in the mix, resulting in the need for the
/etc/hosts files (for each setup) as well as a LAN trace when the
resolution of the hostname takes place (in case DNS is somehow being used
in an unexpected way, or in case some other protocol is somehow being used).
Good luck.
On 10/13/2010 04:06 PM, Easgs wrote:
>
> Just to confirm, you’re trying to VNC to a remote machine, right? yes
>
> Something other than the box from which you are connecting? it doesn’t
> connect to any pc when using static IP, the problem is that there are
> several pc in the network and we use vnc to give remote support, all the
> pc are windows xp boxes.
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJMtjLwAAoJEF+XTK08PnB5e+oQAI3vlDBsl+FvL/9M4AOPHcJJ
/HfAuD2vn2UQXVAVAz8O91k5n2MuR2We1UrPRwLgpC1uOWyhVAjqaQp92L797RQI
ixgOdBD4ArSW9rSCYd6ZXcC7/OGTZowo7NBWx4WtQEcNY80FeJiB1N3OCAPIYirJ
6HoNH007USoSzVWKR+OrIIBHy/ku/502OUIPNa8J9K2Qt7aGqZxxDlA/W4B6wVFd
Xf5ubk55UOh7SS/fi2/lpssVvXvzlasQZ0yrPmOqivE0gFOMsbx0yL8Bklx51M8P
RslgYLUxlfY1sRcqAHIozufrNC7Snv9Y4DhMx93r3kReYr+u1fVtQzxHAp7hMf8j
RcOg1AljNyAIeFQj6hLlSqX/T2CdmUqPu9oiFCICjIy0IPX41lwiT5lh9qF2/Nl3
fHkVhR7563g3gKIMoLsmqfFGzB3ZZ2zWGnaqShor1zAhf2IxlVZdateC8b3VGbbh
z3pXEAXwwMGOHkhMcBX34jG/GQHFwNYV4XOW9ctQocVP6uf70ApTslvjKdDd7WEK
kVoXHs/8aMkA+RwQzvqLfiGzSGcpIIzE06d30HDBlZj7TBqVXNnzYBSSv0+mPekH
7BydNxv2qCTks2aPfd8+U7wvEI2VmkuLzWjhnTgLWeeEHGE8l0F90sxZ5hNDpV8d
BvEsrTNbmEA/XxuH/HJu
=obS8
-----END PGP SIGNATURE-----
Just to get a few possibilities out of the mix, in addition to ab’s Qs:
Is the client machine attaching to the server from across the Internet or is it in the same local LAN/WAN network as the Server
is in the same LAN
If it’s “local”, do the client and the server belong to the same IP subnet (LAN) or different subnets (WAN)?
it is in the same subnet
this is a windows domain, the server is a windows 2003 server, all machines are windows xp, only my pc is a openSUSE 11.3 box, the domain controller is the local DNS server, and everything is working fine in the rest of pc of the network, the problem is that there are a lot of pc and vnc is used for remote support, and it is easier to work with hostnames.
It could be the comms from the DNS server in the domain controller are the problem, which I don’t understand and can’t advise on.
Here’s two different thoughts:
I would try this diagnostic experiment: turn the openSUSE firewall off and see if there’s a difference (domain controllers use an extra port or two). Just to see if there’s a “port” issue.
I would also turn on wins in the file /etc/nsswitch.conf in the openSUSE box. Locate this line in the file:
hosts: files mdns4_minimal [NOTFOUND=return] dns
and make it like this
hosts: files mdns4_minimal [NOTFOUND=return] wins dns
And of course I would reboot the windows server and the openSUSE box (twice in sequence) after the wins alteration, because I’m so impatient.
I have this line in the smb.conf file
name resolve order = bcast host lmhost wins
How it is affected if I enable wins in the nsswitch.conf file?
disabling the firewall didn’t work
Without it you generally can’t ping by hostname. Here is more about wins. If you try it, use my format, not the format on the link.
disabling the firewall didn’t work
Just a passing thought.
Ok, it worked after editing the nsswitch.conf file as swerdna said, thanks a lot for the help