You could perform a "netstat -a" from the command-prompt (this will give you the IP Impulse is connecting to)

Then preform a "tracert" also from the command-prompt (eg. tracert xxx.xxx.xxx.xxx <-- the x's are the IP) to find out where the "bad hop" is in your route to SD.

Knowing that, you could add a custom route statement to your PC to change the route your PC would take to SD in order to bypass the "bad hop".

If my instructions above make sense to you, try them and you should have success. If they don't make sense to you.......what can I say? I'm sorry.

thanks,

the Monk