Bug 201874

Summary: vncconnect doesn't actually connect
Product: [Fedora] Fedora Reporter: Will Woods <wwoods>
Component: anacondaAssignee: Chris Lumens <clumens>
Status: CLOSED RAWHIDE QA Contact: Mike McLean <mikem>
Severity: medium Docs Contact:
Priority: medium    
Version: 6   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-08-11 15:50:52 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

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.