Question Locked

How to make ISA Allow Non-Domain Users to Internet?

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi! I'm currently configuring a network at my workplace. They're running a Windows Server 2003 Domain with an ISA server in between it and the internet. The network runs on the 10.0.0.1 network and we have about 300 workstations. All workstations have certain restrictions since it's a school, so for example, instant messaging and other protocals are disabled for the students. Port 80 for internet access is pretty much the only thing the students have, thanks to the ISA server [ISA Server 2000].

We also have 9 wireless access points around the school, that have 192.168.0.1 as their network, but have DHCP disabled, and a cable going to one of the 4 jacks on each, so that our main DHCP server can give them a 10.0.0.1 address like the school has and allow wireless domain members into the network.

The problem is that we want people who connect to the wireless network as a visitor to the school to have access to the internet and ALL protocals they need, bypassing the ISA server. Right now, if you connect to the wireless, you get a page cannot be displayed screen from the ISA server. You NEED to be a member of the domain to get through.

I appologize in advance as this is probably really simple, I've just never used an ISA server before for this and would really appreciate any help :) Thanks!

6 replies

by fred123456

I have used the MS ISA server briefly, but I don?t think you can tell an ISA server to ignore clients that are members of the domain. Even if its just a pc that was given an IP address from the domains DHCP server.

But I see a security issue right off the bat.
If you use the same "Internal" network to give uninhibited access to the internet. What?s going to stop students from finding out and using that connection instead of the school network?
Also, your giving anyone who comes to visit your site IP access to your network. The same network where your servers and clients reside which is bad.
Plus if students find out that this public network is available, then you?ll have a student with his or her own laptop/wifi device surfing the web.

I work in an environment with a similar scenario, we began to realize we had to create a completely separate network for the public access. We still use our networking hardware to support the public hot spots, but we have created VLANS on our switches to support a completely separate IP networks for the public. We also have DHCP running for that network and its IP scheme is completely different from out internal network.

I was called in to a school to troubleshoot a problem that they couln't figure out. It seemed that 24 hours a day seven days a week they were using tons of band width.
A resourceful student had rigged a WAP to a spare network jack in an unused closet that connected to a PC in the computer lab. They had a UT2004 game server running on the pc and were using the schools connection as the host for the game server.

They had done something similar to try and allow guests to use the internet connection uninhibitetd.

by link470

Mhmm, I completely agree with that. The domain however is locked down so you can't browse the network and you can't access the servers or other computers or student files unless the computer is a member of the domain and authenticated by one of the user accounts in Active Directory. Anyone else however who brings a laptop in who is not a member of the domain, we would like to have Internet access to. The DHCP server will give them a local IP, and they'll be on the same network physically, but they can't access any resources.

That would also allow the students to come in and use their laptops, and yes, they will be able to access the internet and other protocals from their laptops, but that's ok with Administration. They're allowed to use them around the school and at lunch at a hotspot, it's just the school network and school machines that are locked down because we don't want classes inturrupted. The machines on the network are strictly for school work.

Thanks again for your quick reply! Good calls on the security loopholes, hopefully I've added enough this time. I'd just like to have the non domain users not get a page cannot be displayed message from ISA.

by fred123456

I understand the network is locked down, but it may depend on the level of the student.

While in graduate school a schoolmate used "some tools" to gain access to the 2000 Server Network which the IT department swore was secure and locked down.

But he was using a nix laptop and some really interesting software. It took him a week but his biggest gain was when he was able filter the network packets and discover the username, structure for the network.

I think a week after that he found someone with a really weak password.

I love working in schools, the students keep you on your toes.

by link470

I think that may be part of the reason they hired me :P I graduated from high school in 2006 from another high school in the district and was a tech in grade 11 and 12 at that school. They know I can think like a student still at 19 ;) I may have Cain & Abel'd the network a few times in my day, lol.

by cg it

it would be better to install a perimeter router/firewall, have ISA protect the Network have the wireless access points between the perimeter firewall and ISA server.

That way, quests are not on the network.

OR, you can add a 3rd NIC [3rd subnet]to the ISA box which connects to a switch. your wireless access points then connect to that switch. This subnet would be seperate from the school network and protected by ISA.

This discussion is closed to new replies.