What steps will reproduce the problem?
1.click the "torrent" pull-down menu
2.under the "connect to daemon" submenu, select "new connection"
3.enter a known-good hostname that belongs to your running transmission-daemon
server, in my case xaxxon.local
4.name the connection, verify that username, password, and ssl options are
correct for your transmission-daemon server configuration and click ok.
What is the expected output? What do you see instead?
up pops a dialog box that says immediately "host not found" instead of
connecting successfully to the server.
What version of the product are you using? On what operating system?
Transmission Remote GUI version 4.1 on Mac OS 10.8.2
Please provide any additional information below.
This is only related to hostname resolution. connecting to the
transmission-daemon server works completely as expected when I replace the
hostname with the ip address of the server (in my case 10.3.92.100).
I have verified that the host name is correct and resolving to the correct ip
address by going to the terminal and pinging the host name of my
transmission-daemon server. ping resolves the host name to the correct and
working ip address of the transmission-daemon server and proves that network
connection is possible, fast, and stable.
Xan:~ cpgeek$ ping xaxxon.local
PING xaxxon.local (10.3.92.100): 56 data bytes
64 bytes from 10.3.92.100: icmp_seq=0 ttl=64 time=1.977 ms
...
--- xaxxon.local ping statistics ---
11 packets transmitted, 11 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 1.324/1.789/2.534/0.337 ms
I have verified on my windows desktop that the windows version of
transmission-remote-gui 4.1 *DOES* allow me to use the hostname instead of the
ip address, but I can't under os x.
Original issue reported on code.google.com by cpg...@gmail.com on 21 Oct 2012 at 8:01
Original issue reported on code.google.com by
cpg...@gmail.com
on 21 Oct 2012 at 8:01