Getting set up VNC problem

[ckeen]

Okay, so I'm trying to setup my server, and I'm following step by step each portion. By the way, I'm using Ubuntu Server 10.04 LTS as it seems to be the best option. I've had no issues all the way up to the VNC installation. When I run TightVNC from my Windows 7 box, I try to log in and it gives me a TightVNC Connection window that says "Connecting to ubuntu-media-server:1 ... Status: Connection initiated." Then, there's another window that pops up called TightVNC info that says "Failed to get server address (ubuntu-media-server). Did you type the host name correctly?"

It probably worth noting that back in the Putty step (prior to this), that I couldn't log onto server box by putting in the name in Host Name box. I actually had to use the IP address (obtained from my router) as 192.168.1.17 - I also tried using that IP address in TightVNC, and that wouldn't work. Is this a port forwarding issue?

For what it's worth, I'm running a Netgear WNR2000v3 router with the latest up-to-date firmware. This router was purchased a few months ago, and it gave me a bunch of headaches trying to get my blu-ray players connecting to netflix until I updated the firmware.

Any help would be greatly appreciated!

BTW, I love this sight and it's step-by-step directions, it makes it a lot easier for a Linux noob like me.



CK

[Andy Horn]

Hello and welcome to the forum.

My thoughts are that this problem you are experiencing could be something to do with DHCP.

When setting up devices on a network it is always good practice to assign static IP addresses to certain devices such as printers and servers.

I am not sure if VNC will work over DHCP as I always give any device on my network that may need SSH or VNC a static IP address as it makes it so much easier when troubleshooting.

If you have rebooted your router or server the chances are the IP address of your could have changed after the reboot.

My suggestion would be to assign a static IP address to the server and see if that fixes your issue.

Hope this helps....

Andy

[Ian]

Hi Andy,

I was typing up a lovely response to CKs question and as I was about to hit "submit" I saw you'd beaten me to it


CK, In addition to Andy's advice, I wonder whether your issue with TightVNC not being able to connect at all is because of the firewall on your windows 7 machine? Do you have just the Windows 7 one or another one too, perhaps installed as part of an antivirus solution? Try disabling it/them, as a test, and see if it makes a difference. (The port for tightVNC is 5500 by default).

"Port forwarding" is only required if you want to connect to your server from outside your network, say from your work computer or from a friends house.

Ian.

[Andy Horn]

Sorry gaffer .

Mmm I never thought about W7 firewall.

Andy

[Ian]

Well, mine worked as per my guide but I figured I'd throw that idea into the mix anyway. I couldn't think of anything else

Ian.

[Andy Horn]

Mine worked after about the 10th attempt, once I had figured out to use the netbios name of my server as opposed to the IP addy in TightVNC, I mean how thick can you get , the answer was there in front of me in black and white and I somehow missed it

Now I have virtual servers running inside my main server that I can VNC into with ease

Andy

[ckeen]

Thanks for the reply guys. I did get to fool around with it a bit more last night, and I tried everything all over again. I was able to get to it by using the IP address. I haven't ever assigned a static IP address to anything on my router, but this is obviously a smart decision, because as you mention, it can change if the router or any switch reboots.

One of the neat side-effects of this whole experiment is that I'll be learning some nifty things while I have a go at it ... and admittedly, my networking knowledge isn't that great, so it's sure to get beefed up a bit along the way.

So if I actually go in and set up static IP addresses for the server (might as well do the networked printer too I suppose), then I will likely be able to call the server by name instead of just using the IP address? By the way, I used Ubuntu-Media-Server as the name, hopefully there's no conflict in the naming convention I used that would cause any issues there, right?

[Andy Horn]

No worries.

I doesn't really matter what name you give your server.

You need to assign a static IP for the server not your router, your router assigns DHCP IP's to devices on your network by default and should have something like 192.168.x.1 or 192.168.x.254 depending on make and model.

BTW most switches operate at layer 2 or data link layer of the OSI model so rebooting a switch will not change an IP addy on a network, generally switches do not have an IP addy

http://en.wikipedia.org/wiki/OSI_model

And I have attached a nice little picture that helps explain the OSI model.

Andy

[DunkB]

Just as an addition to what has already been said. If your router allows you to specify a start point for assigned ip's set it past the last static ip.

ie.
my routers ip is 192.168.1.1
I've set the first DHCP IP as 192.168.1.10
Which leaves me 2-9 as static ip's

This stops the router trying to assign the ip you've set for your mediaserver to a games console or your mobile phone after a restart.

Hope that makes sense,

Dunk

[Ian]

Hello the Dunk,

You've been keeping a low profile of late. So nice to have you back sir

How the server going? Has it needed much tweaking since you first set it up? Any regrets or things you would have done differently?

Seasons greetings by the way

Ian.