I can't install my static IP from Comcast. Here's how it's set up so far: Modem - SMC8014 Comcast put it in the quasi-"bridge" mode Router - D-Link-655 Connection - Static IP Stream Engine - Enabled WAN IP - aaa.bbb.cc.ddd WAN Subnet Mask - 255.255.255.0 Gateway - aaa.bbb.cc.dde DNS Server - 68.87.85.98 Secondary - 68.87.69.146 Advanced DNS - disabled LAN IP - 192.168.0.1 LAN Sub - 255.255.255.0 DHCP - enabled DNS Relay - enabled Virtual Server - 25, 80, 443, 987, 1723, 3389, 4125 Port Forwarding - [router is not saving settings] SPI - enabled UDP - address restricted TCP - port/address restricted UPnP - enabled PPoE Passthrough - enabled HTTPS Server - disabled Dynamic DNS - disabled Workstation - Win 7 Pro IP - 192.168.0.100 DNS - obtain automatically DHCP - enabled NAT - unblocked Ports Open - 25, 80, 443, 987, 1723, 3389, 4125 I keep getting the error message that the adapter is unable to communicate with the DNS server. Also, I can't seem to save the port forwarding setting when I type them into the router. Everything works when the modem and the router are in dynamic modes. All help will be appreciated.

Stupid question, but where are you trying to assign the static address? In this case it should be on the WAN port of the router, which makes this a router issue and not a Windows 7 one since Windows is behaving correctly. In addition to the static address Comcast should have given you a subnet mask, which probably isn't 255.255.255.0. Also, the reason the router isn't saving your port forwarding info is that those ports are already assigned to a virtual server and can't be forwarded.

Actually, the submet mask assigned was 255.255.255. ... without reference to the final number, which I assumed to be 0. Looking at my notes on the "bridging" I think the subnet mask was 255.255.252.0, which may answer your question. I suspected the conflict between virtual server and port forwarding, and I disabled the virtual server to see it would enable the port forwarding. I still couldn't save the port forwarding settings, so it does sound like a significant router problem. Thanks for your help.