Windows Server 2008 Setup Web/Net Question

May 3, 2011 at 04:59:22
Specs: Windows Server 2008
my network architecture is as follows -> wireless router - > two machines that connect to the router; one of them is the windows server 2008. my question is is there a way to setup a static ip for the windows server machine so when a user enters the ip it connects directly to the machine? maybe a setting in the router? the public ip for both machines is the same which correct me if i am wrong is a setting that is controlled by the ISP.

would some sort of DNS and DHCP option help here?

any suggestions at this point would be helpful.

thanks!


See More: Windows Server 2008 Setup Web/Net Question

Report •

#1
May 3, 2011 at 06:07:35
If the 2 machines are getting an external IP address, there is something wrong with your set up. Open the web interface of the router. Try to see what's happening.

How do you know when a politician is lying? His mouth is moving.


Report •

#2
May 3, 2011 at 06:14:30
one is a desktop machine and one is a laptop. the desktop has windows server 2008 installed with the webserver package and both are connected wireless to the router.

when i goto whatismyip.com for both machines it registers the same ip address.

the network ips (192.X.X.X) are different

HELP?


Report •

#3
May 3, 2011 at 07:29:17
I guess, your public ip address is dynamically assingned by your ISP.
That means, every time, you reset the router, your public ip address will change.

If this is, what you got, you need to use some sort of public DNS services like DynDNS or NO-IP.

E.g.:
If you're using DynDNS at http://www.dyndns.org and create a new accout freely, you have to logon to this account and create a new domain, something like:
myprivateserver.dyndns.org

Then, you have to check, whether your router supports updating dyndns ip address.
If it does not, you can download a windows client, that must be installed to the server. You have to configure the login data for your dyndns account and the domain name, you've chosen.
So everytime, you router get's a new public ip address, your dyndns account will be updated with the current ip address, so that you can access you server from the internet by using e.g. myprivateserver.dyndns.org

You also have to configure port forwarding in your router.
E.g:
If your server has the private ip address 192.168.1.2, and you'd like to access webservices on your server, you have to forward TCP port 80 to local ip 192.168.1.2 port 80.

Accessing the server from your local lan by using myprivateserver.dyndns.org will mostly not function, because most SOHO routers do not have a loopback functionallity for the public interface of the router.

Click Here on HowTo ask good Question to get best Help
Let us know, if the problem is solved !!!


Report •

Related Solutions

#4
May 3, 2011 at 07:35:16
my question is is there a way to setup a static ip for the windows server machine so when a user enters the ip it connects directly to the machine?

Are you trying to connect to the computer to manage it (ie: RDC) or to connect to a share?

If you want to connect locally on the LAN to manage it, enable Remote Desktop access on the target computer, then run RDC (remote desktop connection) on your laptop, enter in the LAN IP (the 192.xxx.xxx.xxx address) of the target in RDC on the laptop and click the Connect button.

If a share, then you need to first have a share, then you would map a drive to the targets LAN address.

If you want to connect remotely from an external location, then you need to configure a port forward on your router. The port forward would look as follows:

forward [port #] to [LAN IP of target]

From the remote site, you would connect to the external IP as provided by your ISP (found by going to what's my ip from any LAN computer) and the forward will take care of the rest.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

#5
May 3, 2011 at 07:36:22
@paul

i did setup a dyndns setup and attempted to use however it failed. is this because i did not setup port forwarding on the router to the windows machine for port 80?


Report •

#6
May 3, 2011 at 07:37:34
@curtis

this is being used for access to my website on the server machine.


Report •

#7
May 3, 2011 at 07:50:14
First of all, it's Curt not Curtis. I would appreciate you using my name, not somebody elses. Yes, it's a sticky point with me.

Remote access or local (LAN) access?

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

#8
May 3, 2011 at 08:38:04
For access from the internet, you must configure the port forwarding in the routers setup, yes.

Click Here on HowTo ask good Question to get best Help
Let us know, if the problem is solved !!!


Report •

#9
May 3, 2011 at 09:21:06
@Curt

my apologies for the name butchering.

yes it is for remote access. just like typing in a url.


Report •

#10
May 3, 2011 at 10:50:09
Ok, what Paul said, you need to create a port forward on your router for port 80. Properly configured it will look something like:

Forward [Port 80] to [IP Address of Web Server]

Where port 80 = http

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •

Ask Question