Win2003 login remotely to FC4 via VNC
I know that there are heaps threads about this topics , but this what I did without any success
This is what I did on FC4 I am logging as root (I know the security implication) First: [root@localhost ~]# rpm -q --info vnc-server Code:
Name : vnc-server Relocations: (not relocatable) Second: The gedit /etc/sysconfig/vncserver Code:
Third: [root@localhost ~]# vncpasswd root Password: Verify: Fourth: [root@localhost ~]# vncserver New 'localhost.localdomain:2 (root)' desktop is localhost.localdomain:2 Starting applications specified in /root/.vnc/xstartup Log file is /root/.vnc/localhost.localdomain:2.log And i run the below command as well [root@localhost ~]# service vncserver start Starting VNC server: 2:root A VNC server is already running as :2 Fifth: http://www.redhat.com/archives/rhl-l.../msg05595.html Quote:
Sixth: Code:
http://img273.imageshack.us/img273/8994/vncviewer5vn.jpg 198.222.168.189:2 The error message that I received when I typed in the ip address for the address is below: Code:
VNC Viewer: 198.222.168.189:Error Note: 1- FC4 box and Win2003 box within the same LAN, the reachability is there (ping each other) 2- From within FC4 I tried : vncviewer 127.0.0.1:2 (same as vncviewer :2 ),,,,,,it worked. 3- I tried to do test by telnet from win2003 : Telnet 198.222.168.189:5902,,,,failed 4- I tried to http://198.222.168.189:5802,,,,,failed as well. I tried to configure from GUI method Desktop - Preferences - Remote Desktop , check the users view and use boxes , uncheck the 'ask you for confirmation' box , set password , then - Desktop - Server Settings - Services , tick vncserver box - start - save , (starts at boot up) Any suggestion ? |
The fact that you can connect from within the Fedora box tells you that the server is running and accepting connections. Also, the syntax you used to connect either via a vnc viewer or from your browser are correct. To me, that suggests that something in between is blocking the connections, and I personally suspect the firewall. I know you said that you stopped the firewall, but does that turn off the firewall or does it simply stop all network traffic? Have a look at the output of iptables -L -n and make sure that the firewall is down.
Along related lines, that IP address looks like a real, routable IP address. Do you have a router that this traffic would have to go through? |
On my system, I have had to deal with a bug in vncviewer that prevents me selecting the particular port I want when tunneling over SSH, using the client option for tunneling.
I cannot say that your problem is the same, but it might be similar. The security of VNC sucks anyway so remote accessing via SSH tunneling is a good plan under any circumstances. Try setting your VNC server to only accept local connections (or, perhaps it is already set that way? Something to check). Then make sure sshd is running. Once you have done that, set up a batch file on the client like this, invoke the batch file, and it will work: ssh -f -L 5901:localhost:5900 myserver sleep 20 vncviewer -owncmap localhost:1 |
Quote:
Code:
http://img103.imageshack.us/img103/2519/screenshot7eg.jpg |
OK, your firewall is definitely off and traffic should flow through without an obstacle.
So that leave the other question, are there any devices like a router between your client machine and the vncserver? And is the vncserver directly connected to the Internet? |
Quote:
only switch between the server and client. To assure that there is no devices between the client and the server, I unplugged PCs from work's LAN and connected both PCs directly by using cross over cable. I assigned private ip address to both PCs (cleint 192.168.1.5 and server 192.168.1.1),still I can not connect The message that I recieved is this : Code:
VNC Viewer:192.168.1.1:Error |
This is weird. OK, here is a few ideas:
1) Check /etc/hosts.allow and /etc/hosts.deny on the server to see if there is anything there that might cause an issue. 2) On the server, have a look at the output of lsof -i (run as the vncserver user) to make sure that vnc is actually listening to the ports you think it is. 3) You also might have a look at the client firewall and see if that might be causing trouble. 4) As jiml8 suggested, try establishing an SSH tunnel between the two machines and then see if you can connect to localhost:X from the client. As a last resort, you might think about ditching VNC for FreeNX. It is a similar concept to VNC, but natively runs over an SSH connection. |
Quote:
did you mean that in your case there was problem on thr vncviewer on your winodws box ? Quote:
and how to configure vncserver to accept that connection. Quote:
|
1- Shouldn't I be a root to add vnc sessions for each users ?
While I was reading this threat Quote:
VNCSERvERS="2:root" VNCSERVERARGS[2]="-geometry 800x600" VNCSERvERS="3:jsmith" VNCSERVERARGS[3]="-geometry 800x600" VNCSERvERS="10:jpeter" VNCSERVERARGS[10]="-geometry 800x600" |
Quote:
Code:
VNCSERVERS= "1:root" "2:jsmith" "10:jpeter" Quote:
And just a suggestion, you might want to reconsider running a vncserver session for root. VNC has little security and it would personally make me nervous to have a root session automatically started. |
Quote:
Quote:
Quote:
normal user I have not got any problem) |
If the starting line I posted doesn't work, you might try this:
VNCSERVERS= "1:root 2:jsmith 10:jpeter" (note that evertying is in a single set of quotes). ARGUS="geometry 800x600 -alwaysshared" I saw someone post this as their example of starting vncservers. |
All times are GMT -5. The time now is 03:40 AM. |