@FDMilwaukee -
Interesting. It looks like the target server is using Parallels virtualization (as opposed to Microsoft Terminal Server or Citrix) to provide virtual Windows user sessions. This being the case, it is entirely likely that your IP address has been put on a blacklist by your client's ISP.
The "administrator" contact at the IP address you're doing a tracert to is
[email protected]. Originally this seemed like it might be the ISP but blu-echo.com appears to be a company selling warranties into the trucking industry or providing sales tools for that. Is this your client, perhaps? If not, the ISP is providing virtual hosting with multiple domains on the same IP. This is pretty common. If this is the case, blu-echo.com is simply the first host on the list.
The ISP actually appears to be DreamHost in Brea, CA. They have a support site at
http://wiki.dreamhost.com/Category:SupportWhere to go from here? Getting a new IP would be a big help, but that often isn't an easy task. Simply restarting your cable/dsl modem is not likely to do it. In fact it should not do it if your ISP has their routers configured well. Your local router/cable modem MAY have an option to request a new IP but most do not. If it has an option to emulate a custom MAC address, which many do, then try this:
1) disconnect the cable modem from the Internet
2) change the MAC address of the cable modem (write down the original one as you may need to revert to it. Simply changing the last digit is enough.
3) if you have the option, force a refresh of the DHCP lease. This will fail since you're not connected to your ISP but, with luck, it will flush the old lease and corresponding IP address from memory.
4) cycle the power on the cable modem
5) reconnect the cable modem to the Internet
6) refresh the IP address lease again
A few ISPs keep strict control over MAC addresses and may not assign any IP to a piece of hardware they don't have in their MAC address list. If this is the case with yours, revert back to the original MAC address so you don't end up hating me for breaking your Internet service.
Failing that, and assuming there's a web site already configured, your best bet is to hit the server via a proxy. Try
http://azurf.com/ or
http://proxify.com/ or any of the proxys at
http://proxy.org/. This should allow you to see the http or https Plesk Control Panel that is being run on the target server. It probably won't support Remote Desktop. If you need to use Remote Desktop to set up Windows IIS, the fastest approach might be to get hold of DreamHost and ask them to pull your IP off of their blacklist.