Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Firewall falling over under win2000 server 2

Status
Not open for further replies.

flipineck

Technical User
Dec 23, 2002
26
GB
Hi everybody,

Our small company recently decided to go it alone in the big bad world of the Internet. Initially we were going to use a lone computer using Win98 Internet sharing ( we're on peer/peer and don't really need much in the way of domains ) with that computer being the access point, with Sygate Firewall Pro running on it to act the 'bouncer'.

It was decided by one 'in the know' employee to get the lone computer to run Windows 2000 Server software, after a bit of fiddling we got the thing up and running, great.

We also got the Sygate firewall Pro running on it, only the trial version, we've yet to commit to a certain firewall and anti-virus ( our AV is a few years old, and to my knowledge nobody has ever bothered to update it, 'We're not NASA is the general reply' ).

Everything so far is great and dandy, but!!

The nature of our company uses a lot of the Internet, which the general public has access to. We've had several issues with people going to unfavourable sites (rotten, kazaa software, face-party, things like that ).
Now I know you can block certain IP addresses, which I did, but when I get up to about 25-30 blocks, the Sygate firewall crashes, blocking everything, I tried this about 5 times but ended up with a line of people behind me ready to 'do me in'.

The computer we are using for the access point is a normal desktop, 1.6 GHZ CPU, 256Meg of RAM with a 40Gig HDD.
What do you reckon?? normal servers look like small cupboards, double CPU's ect.

Are we asking too much of this type of computer to be a server as well as guardian of our workgroup ( we can sometimes have 15-20 people accessing the Internet at any one time) or do you think we've just not configured the thing right?

If you've got this far, thanks, I tend to waffle. The answer could save me weeks trying to resolve the problem and then finding I've been pi***** in the wind.

Cheers.
 
>It was decided by one 'in the know' employee to get the >lone computer to run Windows 2000 Server software, after a >bit of fiddling we got the thing up and running, great.

Are you using the server machine only for a internet gateway? Bit of an overkill isn't it?

>The computer we are using for the access point is a normal >desktop, 1.6 GHZ CPU, 256Meg of RAM with a 40Gig HDD.
>What do you reckon??

The computer is fine. Try Sygates support/faqs its probably just a bug in the software. (Tech support will usually help you even when trialling the software). You may be better off using proxy software with intergrated firewall such as
I usually stay well away using any kind of server for a internet gateway/firewall. & are cheap/free linux distros that can be used on low end pentiums.

Ash.
 
At first we were just going to have a computer with Win98 as an access point for the Internet with connection sharing, firewall on ect. I also looked into using Linux as the operating system, also running the firewall.
'One in the know' stated we must use Win2000 server, and so we have a peer/peer network going through a 2000 server. We're only a relatively small group and so no-one is a server whizz-kid, just plenty of long nights with a big book open.

When we get our current issues sorted, we'll then look into setting up domains with client/server and VPN. If we've got the stuff we might as well use it.

Thanks for the info, at least I know that I'ts a software problem and not hardware.
 
Why even waste your time with trying to 'hack' up an internet connection via ics? For the amount of $$ you shelled out for M$ w2k swiss cheese server you could have purchased a linksys router and switch/hub. Many smaller companies employ this very sucessfully.

A simple approach would be to install a cisco router and control user access via ACL list blocking ports or even entire IP ranges. I would never, 'never', directly expose any M$ server directly to the internet. Firewall it via hardware - NAT or otherwise.

For hardware/software combo's check out or
~Rick
 
Thanks for the replies,

Both have been equally useful in providing further avenues of information and time saved looking into areas not needed.

I must admit I like researching issues 'before' implementing it. I'm not MSCE/CISCO trained but know enough to know how much I don't know, it seems others don't. On the good side is the amount of knowledge I'm picking up, hands on so to speak.

Thanks for the time you've saved me.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top