I have configured one of my sites which I am going to host on my server to use the dedicated IP http://67.19.188.20/ in Helm.

I have RRAS configured on my main IP, and I have added permission for port 80 (HTTP) to work for this new IP (http://67.19.188.20/). For some reason, I still cannot access it internally or externally. Is there anything else I need to add to access it?

The reason I want to do this is so I can test the domain before I change nameservers.

If IIS is doing Name based Webserving, I wouldn't serve the site up because it wasn't requested.

I'd double-check the site in IIS Manager and make sure it's been configured properly. Then, check Helm's error logs. Sometimes it can be a bit flakey with dedicated ip addresses. In some cases, I've had it add a dedicated ip identity instead of replacing the shared identity.

The strange part is it doesnt even respond to a ping though?

Do I have to "add" the IP address anywhere in Windows, before assigning it in Helm?

Well, yes. It would have to be added to your network interface as well as Helm. Though, I was under the impression that this was one of your already-available IP addresses.

If it's not responding to ping, then it might not be configured properly. Check the TCP/IP properties of your Local Area Connection adapter. Click Advanced and make sure all of your IPs are listed in the IP addresses section.

Under "advanced TCP/IP settings" I have only my main IP listed. Should I just add my other 4 IPS here?

If you plan on using them.

lol

OK, I have now done that - is there anything else I need to do before I can use them?

A sacrifice to the Server gods.

Actually, your done.

I have a 5m patch cable burning as I type this

Excellent, now onto the next hurdle!