The ports are not physical, but logical. Port numbers identify services that servers host eg. mail on TCP port 25, web browsing on TCP port 80, secure web browsing on TCP port 443 etc. Combine an IP address and a port number eg. "207.46.199.30:80" and you have all the ingredients required to make a connection to that server and begin to access it's information.
It seems that IE is trying to suggest that these ports are being blocked by the computer itself ie. personal firewall software running on the affected machine is blocking outbound connection attempts to (presumably) anywhere on TCP ports 80, 443, 21 etc.
I think this could just be leading us down the garden path...
IF the test to try browsing to 10.1.1.1 worked, then this confirms that your new NIC is working okay AND outbound connections on port 80 are also functioning.
What happens if you do the following:
Start -> Run -> cmd -> telnet 207.46.199.30 80 (hit enter)
The expected behaviour is a blank screen with a flashing cursor. Wait long enough and you should get dropped back to the "C:\>" prompt. If this works, next try:
Start -> Run -> cmd -> telnet
www.microsoft.com 80 (hit enter)
You can also try the following:
Start -> Run -> cmd -> tracert 207.46.199.30
AND
Start -> Run -> cmd -> tracert
www.microsoft.com
Both of the tracert tests should get at least 12-15 hops before they start timing out.
Could you try these and post a transcript of the results up here?
Thanks,
The ASX Gorilla.