IP Address redirect HTML code

[jordanspringer]

Hey,

Trying to create a website that will be only accessible from my work. The computers at my work are all on a LAN, with a certain IP range. The site I am making will contain confidential info for employees only. I am trying to make it so the site will only be accessible from work, and no other computer. Of course, at work we have like 200 computers on a similar IP. Just wondering how to make a script (in HTML) that would allow access to computers with a specific IP range, and anyone not in that range will be redirected.

Thanks

[Banjo]

It's impossible to do it with just plain HTML. It has to be server side. Do you have a scripting language like PHP installed or the ability to set up permissions on the server?

[jordanspringer]

I'm pretty sure I dont. I know what i'm doing when it comes to HTML but nothing further. I just thought it might be possible, similar to how I was able to make one to detect screen resolution with redirects, thought I could with IP Addresses.

[Truman]

What about setting the IP range in IIS?

[night_stalker_z]

http://www.rgagnon.com/jsdetails/js-0019.html

http://www.javascriptkit.com/script/script2/displayip.shtml

Tells you how to find the IP address. It can easily be by passed if you look at the source so server side detection is better.

[offroadaaron]

why cant this just be a lan setup website then? an Intranet site and not an Internet site!

otherwise you just make it accessible only via your (the works) external IP address of your service and not via the LAN IP addresses.

[jordanspringer]

  offroadaaron said:

why cant this just be a lan setup website then? an Intranet site and not an Internet site!

otherwise you just make it accessible via the external IP address of your service and not via the LAN IP addresses.

because i am just an employee designing a small website tool to help myself. i dont have access to the local intranet.

[offroadaaron]

well then block everything except for the external IP address of your work, server side. Apache can do this and im sure IIS can aswell.

you cant do it via LAN IP address.

One - The LAN IP address isn't whats shown on the net when the packet is passed to the server (fairly sure).

two - Anyone could be using the same IP address as you on a LAN.

[panicswitched]

i wouldnt recommend putting any confidential info online with a simple ip protection it really should be a internal intranet only site

[jordanspringer]

  Felosis said:

i wouldnt recommend putting any confidential info online with a simple ip protection it really should be a internal intranet only site

it is also password protected.

[offroadaaron]

  Felosis said:

i wouldnt recommend putting any confidential info online with a simple ip protection it really should be a internal intranet only site

  jordanspringer said:

it is also password protected.

yeah still wouldn't, I agree with Felosis.

[night_stalker_z]

  jordanspringer said:

it is also password protected.

Using JavaScript?

[panicswitched]

as said above, it would be best to setup a dedicated machine for this, even if it was a spare low powered workstation since you can put it on the lan and it would be filtered from the internet by your router/firewall

[winrez]

As long as it is a up to date server OS (Server 2003 SP2 or above) there should be no reason not to have a intranet on the internet (Extranet) as long as it is password protected

thousands of companies do this daily with no problem.

you could also setup a VPN from your work to the remote server then set the remote server to accept only your works internal lan IP's for connection to the website

Edited April 21, 2008 by winrez

[panicswitched]

im sure there isnt a budget especially to buy a legit copy of server 2003

and if its only purpose is for internal use why risk a leak online? if its specific to your business you stand loosing business

[Leddy]

You can just allow access to the external IP of your work in IIS or whatever you're using. Don't use javascript redirects or javascript passwords, use the permissions handling in your web server software. It's a lot safer.

[winrez]

Does either location have a static IP on the internet?

[offroadaaron]

  winrez said:

As long as it is a up to date server OS (Server 2003 SP2 or above) there should be no reason not to have a intranet on the internet (Extranet) as long as it is password protected

thousands of companies do this daily with no problem.

you could also setup a VPN from your work to the remote server then set the remote server to accept only your works internal lan IP's for connection to the website

yeah companies do this via VPN and such not just via normal html password and IP address. I mean yeah its fairly safe and all but honestly I wouldn't do it (not if there is information that the company doesn't want to be leaked) unless a VPN was setup. That way everything is encrypted and there is a tunnel straight through to the server.

[jordanspringer]

  night_stalker_z said:

Using JavaScript?

using .htaccess

[bolerodan]

This is should never be done directly by a web master or within the html level of things. Contact your network administrator. This should definitely be set up on the works intranet. Your network admin can configure the routers / firewalls to do what you want.

[[bear]]

the best way to do this would be to use apache directives to block certain ips, but to ensure true security you should flip ssl on and then just write a simple session header in php that will be included globally across the entire template.

[Rohdekill]

  jordanspringer said:

because i am just an employee designing a small website tool to help myself. i dont have access to the local intranet.

If it's just a tool only for you, put it on your pc, with IIS on, and limit ip to only your pc. I'd also re-read your your I.T. useage policy. You could be terminated by just accessing an outside website and/or hosting a web service.

[night_stalker_z]

  jordanspringer said:

using .htaccess

Try using this.

http://www.anyexample.com/linux_bsd/apache...p_addresses.xml

[rson451]

since your work most likely has nothing but local ip addresses (10.*, 192.168.*, a few others) internally and if you are only going to have static html pages, you can just share the web directory with windows* to allow other computers on your network to access it. under this assumption that your company is using internal ip addresses this page will not be accessible outside your router unless it's specifically forwarding incoming traffic to your computer for whatever reason--and even so because you arent running a web server they wouldnt see anything.

i highly recommend you speak with your network admins if you really want to set up a web server and all. being a net admin myself, i know this sort of thing can be a bitch from a management standpoint if you don't know about it before hand.

*it's been a while since i've used windows so take this with a grain of salt.