| reply to tipai33
Re: Charter business blocked ports While it is true that the ports aren't blocked by Charter it looks like you were using port forwarding on the previous device to point to your router. Generally speaking, the routers Charter supply are configured with port forwarding and NAT turned off. A customer can request that port forwarding be turned on but will have to designate the IP and port for the Charter device to forward to. That may have to go to your sales rep though because there may be a charge to do so. The previous phone techs should have found that though. I could look at the configuration if I had the MAC of the D3G. |
|
| reply to tipai33
Sounds like they really did get it in bridge mode then, if the ports are still showing blocked even on that PC (barring the windows firewall anyway) then I'd say you are correct and charter is blocking the ports before they even reach the modem. It sounds like you have already run through all the "that's so simple/dumb it couldn't possibly be that" types of potential causes.
I don't know if there would be anything particularly useful in the modems web config which should be at 192.168.0.1 if they left it at default (according to the manual), but it might not hurt to check its firewall/NAT settings anyway assuming charter didn't change the default username / password.
If you can access the SMCD3G's web configuration and are feeling up to it, you could try pulling the Netgear and turning the SMCD3G's router functions all back on then trying its DMZ/Forwarding settings just to see if the bridge mode in it is horribly broken... |
|
| The password is changed upon installment of the device. Only a Charter rep will be able to access it as the passwords are account specific. |
|
|
|
bdnhsv
join:2012-01-20
Huntsville, AL | reply to tipai33
tipai - did you manually enter all the IP info into your router for the WAN interface using the info Charter provided? (they should have given you IP, subnet, GW and DNS to use - can't assume you can re-use the DNS you had before necessarily). |
|
 BD
@comcast.net | reply to tipai33
Have you manually entered your static address into the WAN side of your router? Charter should have told you which address to use, default GW, DNS, etc. |
|
tipai33
join:2010-01-25
Taylorsville, NC | Well after a total of 14 phone calls, 5 techs on site, 4 different modems (tried in bridge mode, static IP with DHCP and without DHCP, and dynamic IP) and even a residential modem the issue is resolved finally after 2 weeks of headaches!
Had to backdoor and get a local network specialist from charter. Around 4 hours of running a series of test it was a rare, weird issue. Everything was setup correct on my end but it seems the devices that needed special ports opened retained ghost information from our original modem (from December) in the nics.
The fix: I setup the wan static info in each local device, connected directly to the modem and then went online. Then unhooked our device from the modem and re-setup our lan static info like it was (nothing different than before though) . Then connected back onto our local network and the ports magically were open finally.
The guy that helped me through this mess said it was very rare and he only has seen this issue on servers running 2 nics but none of our systems have 2, only one. |
|
