Showing posts with label remote access. Show all posts
Showing posts with label remote access. Show all posts

Wednesday, 18 April 2012

How to Port Forward on a DLink router for your server

It just hit me that most people in the world use Windows, (duh) so i had better do a quick tutorial on
port forwarding for various servers on a non-apple router, i will be using a DLink as an example.
Port forwarding on a Dlink is just as simple and straight forward as on an Apple Time capsule
or Airport Extreme.
Why would you need to Forward a port?
Simple answer: so people can access you server from outside you LAN or Local Area Network.
So lets get to it.
Note: this tutorial was requested by a Minecraft player i know by the name of Veyleus. ~Hope this helps :)

What you will need >>>

  • Username and Password to your Dlinks admin page
  • 5 minutes of time if all goes well
  • 7 minutes if you have trouble and need to ask a question on the mini-forum

Step 1, how to access the routers admin page:



First you need to determine if your Dlink will let you access the admin page via wifi.
Some dont allow this for security reasons. But you can change that setting.
Open up and browser and type in 192.168.0.1 this is the default address for a Dlink router
For a Linksys and most other router its 192.168.1.1

If you get a page not found or and you cant connect and itsnot prompting you for a username and
pasword, then its probably not allowing wireless administration. To fix this find an old Ethernet back in the back of your desk drawer and plug in one end to your computer and the other to the back of your router in the Ethernet port. (Assuming that you have a laptop and can go to where your router is or have a long enough Ethernet cord)

Then just enter the same address: 192.168.0.1 in your browser.
It should supply you with 2 fields to enter you password and user name.
The default to Dlink routers is Username: admin Password: private

But normally the password is not the default one, you have to know that password or ask someone who does.

If all go well the admin page should be served up.

Step 2, forwarding the port:

Click the "Port Forwarding" button on the side, a page similar to this should be displayed



Move down to where you see a table like this:


Pick and name of you choice. e.g. Mincraft server.
Then for IP Address put the local ip or you computer, you should know how to find the local ip of your computer but if you don't, drop me a comment. 

Under ports to open:
Put a range of ports instead of just one port, i find it works better for server FTP servers and Minecraft.
For Minecraft i would put the ports like this: 24000-26000 assuming you Minecraft server is running at the default port of 25565.
Put the same port range both the TCP and UDP fields.
You can leave the "Schedule" and "Inbound Filter" selection boxes as they are shown in the image.

Step 3, saving changes and testing:

Click save changes at the top and let your router do its thing and reconfigure.

After that to test it, turn on your server and test it with your local ip to confirm it is working and serving.
Then find your external IP and whatismyip.com and then you that ip to connect instead.

If you can connect to your server using your external ip then grab a bag of pretzels and a glass of Koolaid and just marvel at how you were able to get it to work the first time you tried it :)

But things never work the first time with me so if you have any trouble, drop me a comment and i will see if i can help.

Trouble Shooting:

Some routers may not support ranged port forwarding, so instead of putting 24000-26000 for the ports, just put 25565 or whatever port you are looking to forward.

Some routers may also not allow outside connections from your local network. So you might need to go a to a friends house or an internet cafe to test it. But this is rarely the case.

Make you that you server is running on the port you think it is and that you port forwarded that port.



Thursday, 23 February 2012

VNC, IT Class 1, Installation


I know this post is something like a week late, but I'm not going to apologize. Mainly because I have found that if you keep making apologies and excuses every little time you’re late or something like that you will spend you time making excuses all your life and won't be able focus on the task at hand.

Well enough of my philosophies,  on to the review/tutorial.

So I have done some thinking about how I am going to run this internet related software training course and like all other things that have a beginning, it will be a bumpy yet I hope in the end an information filled and helpful experience.
So now, if you haven't read my introduction to this course and what it will be about in my last post, you should. It explains just what we are going to be doing throughout the course.
To summarize it all here; we will first learn how to control all your computers with keyboard and visual screen feedback from anywhere in the world. Even if you are not traveling you can easily access and control the desktop downstairs with your laptop or any other computer on your local network if you are admin of that computer. We will be working mainly with LAN or Local area network applications for the start of this IT Course. 
Later, we will get into how you access things like personal file servers, IP-cams, remote login from outside your home, web servers and more. 

Now why VNC is such, I think an interesting topic, is because there are so many ways to go about it. If one way doesn't work, for instance, the other will. VNC will work on virtually everything Windows, Mac, and Linux. There is even a VNC viewer and controller for iOS devices! This however I don think is free, people have to make a living you know :p
So no matter what OS you’re on, your still in luck.

I think I can write this tutorial, so that any user on any OS will be able to follow it. Certain things that differ between Mac and Windows for example, I will point out.


Getting started, what you will need:

  • - At least 2 computers, preferably same OS but if not its ok.
  • - An Internet connection with some bandwidth (to download the programs and..... DUH!)
  • - 25, maybe 30 minutes of time if you follow this tutorial
  • - 6 hours of time if you want to do all the research and experimentation yourself :p 
  • - Basic knowledge of general program installation for your OS


Next, programs you need to download:

A complete VNC remote control system is comprised of..... you MAY have guessed it, a server and a client or viewer. The VNC server will run on the computer that you want to view and/or control. 
The VNC client or viewer will run on the computer that you want to view and/or control from.

There are many clients and servers out there for all OS's both free and commercial. The programs I will refer here will be free,  however, if you enjoy this tutorial and its outcome, or want to use VNC on a larger scale for school, work, or play, there is no reason you shouldn't buy the good stuff from the creators.

Because I am on a Mac, and posting this from a Mac, Mac OS will be my forte, but I have done VNC on Mac, Windows, and Linux. 

For Mac, go ahead and download these programs:



For Windows

  • RealVNC Free addition (Download page, server and viewer available from here)


I won't go into Linux unless specially requested by a member's comment

Program Installation:

For Mac,

Vine Server installation
The Installation is pretty straightforward. In the end you should end up with an app, which can be run from anywhere

Chicken of the VNC
This program is also in the form of a .dmg, just drag the .app to you applications folder.

You would probably be best off to install both the server and viewing on both computers. That way they can act as both if you need them to.


For Windows, 

If I remember correctly there was nothing complicated about the installation of the server and viewer on Windows.

Also install the Server and viewer on both machines.

Note: A Windows VNC server will work on a Mac VNC viewer and vice versa.


Seeing as this post is getting quite long, I will break it up into three parts; Installation, Configuration and troubleshooting/options, two of which I will write at a later time. The Configuration post I think will be the most fun.
Stay tuned, or rather subscribed for my next post on the configuration (the fun part, where we'll actually get something done :)