Setting up guest registration on a network

[fifedesigns]

I was wondering if someone could point me in the direction of adding a registration page to my guest network. I would like to monitor websites, etc to prevent any fraudulent activity on my network. Thanks in advance.

 

[mattjones1]

Hi,

Anything is possible if you are willing to invest time etc.

When you say registration page how exactly do you mean? Talk me through a step by step process as if you are the user connecting and using resources/services on your network. i.e:

1. Log on (local or domain user?)
2. Connect to Wireless network (encryption? - key provided?)
3. Open IE
.....and so on.

Can you provide me with some details as to your network setup? ideally:
Server(s) OS
Is your server an FRDC? do you have a secondary DC? any member servers?
IIS configured on FRDC/DC?
Workstation OS
How many users/workstations?

If you have a guest network and wish to monitor web useage, in achieving this we must establish a way of highlighting an individual user - in order to know exactly who has accessed what. A registration page etc. is pretty straight forward and could be achieved with something as simple as PHP linked to a MySQL/SQL DB. Enabling a user to register and also login etc.

Matt

 

[BrokenAtari]

If it is a wireless network you could set up a radius server to deal with that.

 

[mattjones1]

BrokenAtari - good suggestion! Only issue I could see with that is if the user needs access to other resources across the network e.g. shares, printers etc. the point of using a radius server for authentication would be deemed pointless, if this were the case, as you are allowing more access to a network than the a Radius setup is meant for.

 

[BrokenAtari]

You could put them on a different subnet.

 

[mattjones1]

Again, as long as they don't require other service from the domain.

We may have gone way overboard here and 'fifedesign' might be wanting something for home. ha ha!

 

[BrokenAtari]

Put a computer designated as a firewall + sniffer in between the public network and his network. Then adjust the firewall to allow certain features. Have a special dns running on the firewall computer.

 

[mattjones1]

'special DNS'?? DNS is DNS, you can have different types of records.

Lets wait and see what he actually wants to achieve.

 

[BrokenAtari]

'special DNS'?? DNS is DNS, you can have different types of records.

Lets wait and see what he actually wants to achieve.

I wasn't literately meaning "special DNS". I meant that it was only for the public. (A special purpose)

 

[krone6]

Why not just user account permissions? Guest accounts can get on the same network but have no access to printers etc, only web. A little higher up gets more access and so on to adminship. Of course this will open up a less secure network but what's the % of people who'll use your guest account that'll even bother to hack you? They could do it even without a guest network access to begin with, so in the end, guest accounts with permissions might be the simpliest.

(first post btw... woohoo a normal forum)