Bug 201874 - vncconnect doesn't actually connect
Summary: vncconnect doesn't actually connect
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 6
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Chris Lumens
QA Contact: Mike McLean
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-08-09 15:51 UTC by Will Woods
Modified: 2007-11-30 22:11 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2006-08-11 15:50:52 UTC


Attachments (Terms of Use)

Description Will Woods 2006-08-09 15:51:24 UTC
using 'vncconnect=host' (on the kernel commandline) doesn't work properly.

Anaconda says:

The VNC server is now running.
Attempting to connect to vnc client on host metroid...
Connected!
Starting graphical installation...

but a tcpdump of port 5500 and 5901 on metroid shows no connection. Furthermore,
netstat -tl shows that the machine is actually listening on port 5901. vncviewer
can connect to the test machine and the install continues normally.

Comment 1 Chris Lumens 2006-08-11 15:50:52 UTC
Probably shouldn't clobber the correct /etc/resolv.conf with something only
partially correct.  Using the FQDN might work.


Note You need to log in before you can comment on or make changes to this bug.