Make the assumption that all info in this thread is for EDUCATIONAL PURPOSES ONLY!
With that said. An individual has been running a web server on @HOME cable for 6 months or so and is now having some problems. The server is running apache on windows 2000 Advanced server. There are 5 computers on his network and 5 ip addresses. Each has full internet access with no problems. The server runs fine for several days untill @HOME catches on and starts screwing with things. Once they catch on the server must be restarted every few hours to remain connected to the internet. The only other solution seems to be to change the static ip of the server, but this again only solves the problem for a few days at most. It also seems that home.net has blocked connections between some computers on the same inode. I believe that they are using their routers to do this, but only one of my ip's seems to be effected by this. I can ping my friends house with that ip and it times out, but I can ping him from another ip and its fine...Last night I installed blackice defender on the server and blocked the NNTP port scan that home.net secuity was running every few hours. Is there anything else I need to do to block them from seeing my server. I was planning on installing a second NIC in the Server using my primary ip address then setting up advanced server's routing services to supply an ip to each computer on the network. Is this a good idea or should I leave things as is. Would a hardware router be a better solution. I would assume it would be as most have firewalls built in. I just want to see if this is going to work before I spend the cash on more hardware. The server is a dual p2 setup with plenty of resources so thats not an issue. Thanks for your help in advance....
Bookmarks