4

I currently have two production servers. One running Windows Server 2003 and the other Windows Server 2008. When I open the Reliability and Performance Monitor I see a Network section that only goes up to 56Kbps see the image below.

enter image description here

It concerns me that 56Kpbs is the maximum bandwidth that our database server has available. This server is located on the other side of the world, and I have no way of physically accessing the network hardware. I've been instructed not to browse the internet on this computer or download things like adobe flash. This prevents me from doing a simple internet upload and download speed test.

How do I test the servers internet speed from the Microsoft Windows command line or equivalent that does not involve opening a browser on the server? I might be permitted to securely transfer a program after it is scanned for viruses to the server, but this is the least desirable option.

Improve this question
3
  • 1
    The graphs for everything except CPU are scaled. Your server's maximum bandwidth isn't 56kbps, that's just the highest measurement taken in the sample shown. Commented Mar 3, 2015 at 17:37
  • @JamesSneeringer That is good news. However, how do I determine my network speed? Commented Mar 3, 2015 at 17:47
  • You can use tools like iperf, qcheck, etc. Commented Mar 3, 2015 at 18:13

1 Answer 1

Reset to default
3

Invoke-WebRequest http://speedtest.newark.linode.com/100MB-newark.bin -OutFile $env:TEMP

Improve this answer
7
  • Good answer, but this is only for Powershell v3 or above, which the op won't have unless they have explicitly installed it on those servers. Also dumping to `c:` normally can't be done unless you're running from an elevated ps shell. Easy fixed. Commented Mar 3, 2015 at 20:56
  • It seems that Powershell v2 is available for Windows Server 2003 microsoft.com/en-us/download/details.aspx?id=4045 but I've been unable to find a higher version of Powershell that is compatible with Windows Server 2003. Commented Mar 3, 2015 at 21:36
  • Apparently, you can use Powershell 2.0 to install Powershell 3.0. This is according to Tyler's comment on this page blogs.technet.com/b/heyscriptingguy/archive/2012/09/05/… Still I am reluctant to try this on a production server as it is unclear whether the upgrade will succeed on Windows Server 2003 R2 SP2. Commented Mar 3, 2015 at 21:38
  • 1
    @nueverest yeah I wouldn't be touching a production 2003 server with Powershell. Way too much risk for a system that's EOL. Commented Mar 3, 2015 at 21:49
  • I'm experimenting with this command on a Windows 8.1 machine and I'm getting Access to the path 'C:\Users\Username\AppData\Local\Temp' is denied. Commented Mar 3, 2015 at 22:02

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.