|
Yes, it seems like Windows is always using the page file, no matter how much physical memory is available - more physical memory means it takes longer to be swapped out, but restoring a window that was minimized for 10 minutes is always going to the disk. You can that by disabling the page file if you are sure your physical memory is enough for the OS, all applications and the disk cache.
|
|
|
|
|
Finally it happened! After five years of activity, I can proudly announce that my main web site has been victim of a DDoS attack that brought IIS to its knees. Right now, I have set a null route so that incoming traffic will not reach my machine anymore for a couple of hours, and I'm wondering what can I do to prevent or mitigate the effects of other attacks.
I took a quick look to the IIS logs and found out that the majority of the requests come from a handful of IPs. Is there some settings in IIS to drop requests from them? Even better, can I limit each IP to - say - 10 requests per minute?
Do you have other suggestions?
Thank you in advance
Luca
The Price of Freedom is Eternal Vigilance.
|
|
|
|
|
You really can't do anything localy on the machine. No matter what you do to IIS, you'll still be getting the requests and your internet connection will still be flooded with them. You have to contact your ISP to get them to filter out that traffic at their router.
Dave Kreskowiak
Microsoft MVP - Visual Basic
|
|
|
|
|
How can I know the ports opened to the outside of my router ?. Any commands ? I am using windows XP P SP2. Thanks
JIJO BABY - Lets Play C#
|
|
|
|
|
Get out the manual on your router. There is nothing standard that you can type on your XP machine to find out.
Most routers either have a web-based interface that you can get to and find this information, or a Telnet deamon, or a specific configuration utility you run.
Try opening a browser and typing in the IP address of your router, usually 192.168.0.1. If that doesn't work, dig out the manula on the router to find out how to configure it and find the information you need.
Dave Kreskowiak
Microsoft MVP - Visual Basic
|
|
|
|
|
jijobaby wrote: How can I know the ports opened to the outside of my router ?.
There is only one way, that's to audit it from the outside, try this site http://www.auditmypc.com/[^]
I'd love to help, but unfortunatley I have prior commitments monitoring the length of my grass. :Andrew Bleakley:
|
|
|
|
|
Is there a tool/utility that can tell the amount of memory (RAM) an application is utilising on Windows 2000 systems ?
Programming from a spec is like walking on water ......
Its Easier once frozen
|
|
|
|
|
Start / Programs / Accessories / Administrative Tools / Performance Monitor.
Dave Kreskowiak
Microsoft MVP - Visual Basic
|
|
|
|
|
Performance Monitor?
Not on my system (Windows 2000 Professional)
Programming from a spec is like walking on water ......
Its Easier once frozen
|
|
|
|
|
That's where the icon normally is on a 2000 box.
You can also just click Start/Run and type perfmon.msc .
Dave Kreskowiak
Microsoft MVP - Visual Basic
|
|
|
|
|
Hi all
I just had a security problem & hope anyone of u can help me.
I'm using a trial desktop program that connets to SQL server & while it's open my antivirus kept popping up a message saying that there is a port opened by SQL server.
So is there any patch to solve this?
Thanks a lot
Happy
|
|
|
|
|
Normally SQL Server opens ports when it's started, if configured to do so. I suppose it's possible that the desktop program is starting the SQL Server service and the ports are being opened at that point.
You can configure the network settings of SQL Server using the Server Network Utility from the Microsoft SQL Server program group. If this isn't on your start menu, look for svrnetcn.exe typically in the C:\Program Files\Microsoft SQL Server\80\Tools\Binn folder. Disable all network protocols you're not using - if you don't need remote access to this instance of SQL Server, disable everything except Shared Memory. Shared Memory may not actually be shown in this list - if not, just disable everything.
If you still get the problem, it may be that SQL Server has not been upgraded to SP3 or later. Earlier versions still opened UDP port 1434 (used to map instance names to TCP ports) even if the TCP/IP protocol was disabled. If the version installed is actually MSDE (shown as Desktop Engine or Desktop Edition) and it was installed using the merge modules, it may not be possible to apply the downloadable SP4. You should check with the program's author.
|
|
|
|
|
Hi Mike
Thanks a loooooot.
But I had another question,how can the program author solve this??
Should he download SP4 and then re-compile the program?
Thanks again
Happy
|
|
|
|
|
SP4 and recompiling won't make any difference.
Does your app come with and install MSDE or SQL Express??
Dave Kreskowiak
Microsoft MVP - Visual Basic
|
|
|
|
|
Hi Dave
It installs MSDE.. So what is the solution??
|
|
|
|
|
MSDE installs with network protocols turned on by default. You can turn them off at installation time in either of two ways:
If your installing MSDE as part of a Merge Module in your applications Setup:
MSDE Deployment Toolkit[^]
MSDE Deployment Toolkit in Action article[^]
Or, if you're running the MSDE Setup yourself, you can turn the networking protocols off from the Setup command line. See "Customizing Desktop Engine Setup.exe[^]" for more information. But, in the simplest form, the MSDE Setup command line could look something like this:
setup DISABLENETWORKPROTOCOLS=1
Dave Kreskowiak
Microsoft MVP - Visual Basic
|
|
|
|
|
Hi, I just purchase toshiba laptop which has 256Mb RAM. And this machine could upgrade to 2048Mb of RAM. Now I want to upgrade the RAM to the maximum value (2048Mb). But the computer store do not have an accessory (RAM) from toshiba. They have the RAM which produce by another company.
From here, my question is: If I use RAM which is difference from toshiba machine, does it is often cause the system to display blue screen error? Because I know that the blue screen error occure when there is dump memory.
|
|
|
|
|
Typically, as long as it has compatible speeds and timings, you should be fine. Even in systems with generic memory modules, however, you get some dud chips or modules - where the data written isn't stored correctly - which the manufacturer's tests don't always pick up when they're tested in isolation.
After installing new RAM, I therefore normally run a RAM test. You can use memtest86[^], memtest86+[^], or Microsoft's Windows Memory Diagnostic[^]. Run them for as long as you think necessary, but probably for at least an hour (a couple of passes). Leaving it overnight will probably be enough for any problems to show up - I had to limit our DC testing to an hour because it needed to go back into service, but since this is your laptop, you can probably spare more time.
|
|
|
|
|
Mike Dimmick wrote: You can use memtest86[^], memtest86+[^], or Microsoft's Windows Memory Diagnostic[^]
Thank you very much for your comment. Which tool is better to use. In my opinion, I prefer Windows Memory Diagnostic. If an error found, could this tool solve the problem for me or just identify the problem only.
|
|
|
|
|
They're all good for testing RAM. All they do is excersize memory, using various patterns and methods, over and over again, making sure that what was read from each location was what was written to it. None of them are any better or any worse than the others.
If a problem is found, the only thing you can do is replace the bad RAM module. No piece of software can ever fix a failed piece of hardware like that.
Dave Kreskowiak
Microsoft MVP - Visual Basic
|
|
|
|
|
Thank you very much for your comment.
|
|
|
|
|
There is one thing that should be mentioned in this thread:
None of the Software-RAM-Tests is 100% accurate. That is mainly because the modules are not "either working or not working" but also sometimes "kinda working" and there is no way to tell that by a fast check.
There is dedicated RAM-Test-Hardware for professional use, but that comes at a (very) high price (up to several million $US). A test in one of these stations is definitely more reliable, but still there is no guarantee on accuracy more than 99.999%.
Depending on the tool you are using (software or hardware) and the size of the memory module you are testing, a complete cycle for one module might take up to a week to complete.
There is one other thing you need to be aware of, if you are testing your module with a software-tester: You should reset your BIOS-settings to "fail-safe" or the lowest possible setting, or you might accidentally create "false positives", i.e. determine a module to be faulty when it is, in fact, OK.
Cheers,
Sebastian
--
Contra vim mortem non est medicamen in hortem.
|
|
|
|
|
Mike Dimmick wrote: Leaving it overnight will probably be enough for any problems to show up
I have check the Microsoft Website[^] for Windows Memory Dioanostic tool and I found in the Sample run time section that 1Gb RAM just spend around 8 Minute. But why you mention to leave it over night?
|
|
|
|
|
I figure that the longer you run the tests, the more times any given byte is written to, the more likely it is that any errors will show up. It is also more likely to show up any problems which occur when the system is fully up to normal running temperature.
|
|
|
|
|
Thank you very much for your comment.
|
|
|
|