So the server on the network I use (This is a family network) is constantly flooding every computer on the network. This is breaking connections that is making things like gaming impossible. My mother, with a stick right up her ass, wont fix it due to it not effecting her or anyone else other than a little popup and than me. She feels that its my computer however, there is a obvious link of say, Minecraft crashing due to loss of connection with Eset, smart security popping up, Flooding attack. Every time I atempt to send info through the network, I recieve a flooding attack breaking the connections. I know what iP/Computer is causing this, The server is running Windows Buisness Server 2003. I do not have access to the server and gaining access with leave me with the problem of finding somewere to stay. How can I block this computer directly from even pinging my computer. I do not have access to the router/modem ether.
This needs to be sorted but nothing is being done, This is ruining my gaming experience, crashing my downloads and effecting my studies. Please. What can I do to fix this with only a gigabit switch and a computer. Thanks.
If I'm reading this correctly you are saying that a machine inside your own network is attacking other computers. Is that correct? If so, you NEED to unplug it from the network and run some sort of AV software that can be run from a CD. Here's a list of live cd's that I found after 10 seconds of Googling. http://www.livecdlist.com/purpose/windows-antivirus
better question: why is it running BUISNESS SERVER 2003?!?!?!?!?!?!?! it's fucking 9 years later.... get linux server or something, like almost every other server runs..... linux=free, linux=no viruses
I would recommend switching to something like ClearOS, but since you said that's not exactly an option. One of the things that comes to mind is moving yourself to another subnet. Of course this sometimes can require you to already own some decent hardware to do.
Since the SBS appears to already be compromised, you could try just throwing it into the DMZ and seeing how your router deals with it there. You could also try to protect yourself with a hardware firewall distribution like PfSense and isolate SBS to an extent. If you can't do that then I'd make sure you get a damn good software firewall installed. I personally like Comodo as it allows you to create an IP address block list which might allow you to block someone on the LAN as well.
If you don't mind me asking, why exactly are you running such an old variant of SBS when they officially cancelled support on the product line?
I'm not going to go off into how bad of an idea it is to run that old of a server for mission critical systems, but you really should try to convince her eventually to switch. If someone is probing your network and picks up on the fact that you're running an OS that's almost 10 years old they're probably going to find a way in quickly.
Based on what you've said, what I'm about to say is irrelevant but you should still look into it. ClearOS doesn't require you to "learn linux". If installed without error almost 100% of it is webpage, as is pfSense once installed. Maybe try running it in virtualbox and showing her it, but like you said, that most likely won't change anything.
Do you think you can get us a rough layout of your network so we know what you're working with? If you can include any switches, hubs, or firewalls that would help us to try to find a solution.
For now if I were you I would look into getting PfSense to run in a bridged firewall-only mode just to protect you from that machine. If that's not possible definitely look into subnetting yourself outside of the range that the particular server is in, it might solve it.
Another think you could look into is having a switch for everything to plug into, as opposed to a hub (assuming you are using one). If the switch is of decent quality it will allow you to flat out block that server from contacting you or even knowing you exist on the network.
I really am sorry that you're having so many issues with this network, it sounds like a nightmare, another thing you could try doing is switching to a static IPv4 address manually. Since you said nobody else is having this problem, that server is using SOMETHING to identify you and send the data over. Have you tried seeing if this happens in other operating systems, such as a Linux based live CD?
Are the switches of a cisco brand or anything considered enterprise grade?
This network is large enough to where you may want to seriously consider subnetting. You can probably pick up a cisco switch cheap on ebay and program it to stop the server from sending packets on all ports aside from those that you require (and only to those specific machines).
What I also noticed is that your router doesn't have a switch on the back, but a hub. Depending on how good the other switches you have may be, you could have a broadcast storm on your hands since the server is directly plugged into your gateway. If you could get a switch, put it under your router and plug 1 router port into it and then run the rest of your connections off of that switch (not a hub) it could clear up conjestion and solve the issue.
If you don't have the funds to do that, you can try to move the SBS to behind a switch (not an AP or hub) and see if that changes anything. Still though, a 5 port switch should suffice and they're relatively cheap just for testing purposes. If you end up needing programming functionality you're going to need to go enterprise grade though (and should have it if this business expands more).
Here's an Example of what you should try first (moving everything behind the switch instead of having it in the hub). Note: The names of the devices most likely wont match, this is cisco packet tracer so I could only really use cisco devices.
P.S. You can try running Wireshark and waiting until the issue occurs again and you may be able to debug from there (or submit it here and we all dig through it together).
