Sounds like any solution will require logging directly into either the modem or the router. Cable modems are usually proprietary and hard to get manuals for but the ISP will usually walk a person through most setups. I believe that the thing to do (especially because the router is usually needed for connection sharing) is open a hole in the routers firewall to allow requests to come in from specific locations. I've never done that (development machine must be sealed) and details are brand name specific, but once a person is inside the router (http://192.168.0.1/ or http://192.168.1.1/ - the former is for D-link) it may become clear and there are usually help pages, too.
The modem has probably had its DHCP or DNS service disabled somehow.
One thing that might work there is hold in the reset button for a really long time.
The thing is... before 2 days ago.. he could just use the cable modem to connect to the internet... host the CS server.. which only has the static IP...
Now with the router.. every time he creates a server.. the IP is dynamic so it comes out different every time (also sometimes you can't connect).. that's why we don't want the router to be involved for the server hosting...(and normally it just sits on the side unplugged)
We're trying to get his ISP tech to come in and give it a wack...but like all ISPs they like to put people on hold =/
How long do you suggest for the reset?
