Setting up a network with a Suse box & a Windows box
SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
If you followed the above howto, you have TWO different VNC servers configured, one from YaST (remote login) and one from sax2 (remote control). I'd say shut off the yast one (the new session) and try again.
YaST -> Network Services -> Remote Administration
Set this to NOT allow remote administration. This is the one that is giving you the new session. I take it you dont want that, but just want to remote control the pc. For that one, see:
YaST -> Hardware -> Graphics Card and Monitor
VNC -> Allow access... turn on, and accept defaults. Don't forget when you make changes here, you have to reset the graphics system. A simple reboot will do it too.
From the windows pc, you shouldn't have to specify a port or screen number, but just the IP address (or name if DNS resolution).
If that doesn't do it, try opening those ports in the firewall (not sure if you are blocking INTERNAL zone).
Good luck!
Thanks drokmed. Unfortunately, this doesn't work.
I have disabled the remote administartion from Yast, and kept only the sax2 one.
Also switched to the RealVNC. Yet again, when attempting to connect, I keep getting a "Connection refused" box. Also tried to connect from another OpenSuSE 10.2 box - same result. Firewall is disabled. Other than that, the PCs communicate fine (as I mentioned, I was even able to open a new session when it was enabled via Yast).
Any clue?
D.
Hmm I take it you can ping/ssh to it. Here's a few ideas:
When you enabled it, did you click on test? Did the test pass? It has to pass before it will work, then click save.
I've seen one box where test didn't pass. I installed the video drivers from the ATI website, and when I tried to enable remote vnc, xmode just ran forever, kinda hanged, and didn't work on that one.
I just tested from my SLED laptop using 'vncviewer 192.168.1.1' to my router and it worked fine.
Another thought... how many NICs in that machine? You said firewall is off. If there is more than one nic and firewall is off, you will not be able to access the remote nic. Only the local one will work.
Hmm I take it you can ping/ssh to it. Here's a few ideas:
When you enabled it, did you click on test? Did the test pass? It has to pass before it will work, then click save.
I've seen one box where test didn't pass. I installed the video drivers from the ATI website, and when I tried to enable remote vnc, xmode just ran forever, kinda hanged, and didn't work on that one.
Yeah ping succeeds, and so does the test. One thing that has just come to my mind is the fact that the sax2 configuration dialog didn't always come up (just wouldn't open). Couple of reboots solved the problem. Don't know if this has anything to do with the problem.
Quote:
Originally Posted by drokmed
Another thought... how many NICs in that machine? You said firewall is off. If there is more than one nic and firewall is off, you will not be able to access the remote nic. Only the local one will work.
That starts to sound like my problem. I have two NICs indeed, and the firewall is off as it's a company network - no need for it. But still, I am able to access anything via both NICs - one is set up to access my company network, and one - to access some local equipment. Please elaborate - what does the fact that firewall is off have to do with the access from both NICS, and also - if I can access anything via both NICS, then can it still be the problem with VNC?
Cheers,
D.
If NAT, it's built in to the firewall. You have to turn on the firewall to turn on NAT. Otherwise, LAN pc's will not be able to communicate thru the NAT router.
Try turning on the firewall, and turn on NAT (masquerading).
If NAT, it's built in to the firewall. You have to turn on the firewall to turn on NAT. Otherwise, LAN pc's will not be able to communicate thru the NAT router.
Try turning on the firewall, and turn on NAT (masquerading).
I don't use NAT (of course my company does, but it's only relevant for the external router). I basically have two NICS, where the first is connected to the company network, and gets the IP address via DHCP, and the second one has a static address (it's even disconnected right now).
And again - if both PCs manage to communicate in other ways (ping, tftp etc.), why should VNC be different?
Cheers,
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
