said by officederamo:
I know it has been quite awhile since I replied. Although my issue is not completely solved I can tell everyone that there is definitely a conflict with running two nics with one static and a second assigned a lan ip from a router.
On suggestion from Cablevision that helped some was to open the tcpip properties for the static IP, then click on advanced and then assign a value of 2 under the automatic metric.
I know little about this but apparently that will keep the static IP from working against the lan IP.
Hope it helps someone else with the issue.
Woah: That sounds like a single Windows(?) machine connected to 2 networks via 2 NICs, hence conflicting default routes. You can't do that, and the "metric =2" hack is obscuring the issue : this is not a valid configuration.
Run your windows machine's cmd.exe and type "netstat -rn" - if you see 2 default routes (0.0.0.0 / 0.0.0.0), you have an invalid configuration. A windows machine simply CANNOT work with competing default routes - it starts doing random wonky stuff: packets out one interface for one connection, out the other on the next. You MUST configure both NICs statically, and suppress the default route on one of the interfaces (don't ask me how to do that, it's a trivial task under Linux), presumably the local RFC1918 network - and DHCP is a non-starter here.
This has nothing to do with Cablevision providing inconsistent service, but everything with your local network setup being invalid.