A fixed ACL or something will not permit trafic from a subnet other that the LAN side subnet of the device. To end this story, I am told that Comcast ATS is going back to SMC for problem resolution. The problem was only occuring in the D3 offices. To re-iterate, we have five offices, three with the 8014 SMC device and two with the D3 device. Behold they were able to duplicate the problem. Of all the Tier one and two folks I had talked with he was the one who took this issue and got it looked by ATS (Advanced Tech Support). In fact he had had a couple of other customers that were having the same problem. I finally got a Tier one guy (Thank you Josiah!!!) that seemed to believe me and also understand the underlying issue. UPDATE: I have been working with Comcast now for a few weeks on and off on this new install. To swap between Cable and DSL I only need to swap one cable from the DSL device to the Comcast. However outgoing mail is stuck.īasically the 1 to 1s are working but the normal traffic is getting lost in the DMZ or the SMC device (or the return?). MXTOOLBOX.COM can do a port scan so there is two way talking going on there. We could ping the exchange server from the outside world but can't ping the outside from the server. Our exchange Server was able to receive mail, but could not send it out. No client in the internal LAN can get to the internetĢ.Ĝlient in the DMZ can get to the internet.ģ. Yesterday I took our production environment down for the afternoon in a desperate attempt to make it work.ġ. That is one to one nats for our mail servers, Sorenson IP Phone etc. In essence, we duplicated the settings in the Comcast as we had in the DSL devices. We have not had the greatest help from Comcast even at the tier two level (still on going). We cannot get the 22/5 installs fully functioning. We have set the SMC devices the same in each office. The nightmare has been with the two large offices. The small offices 12/2 installs went off without any issues.
For the small offices we went with the 12/2 product and the large offices opted for the 22/5 product. We decided to go to Comcast because they could provide a high speed service at the same cost as the DSL. We have been using ADSL from AT&T for years. Once we had done that, then traffic flowed as expected.Ĭomcast/SMC SMCD3G-CCR Firmware Version 1.4.0.48-CCR Hardware Version 1.01
Previously NAT had been handled by Port Redirection, quite happily, but changing the type of connection meant we needed to change over to Open Ports. It turns out that if our router has the public facing IP as its WAN setting you /must/ use Open Ports. The router has two methods of mapping inbound port traffic to the destination server (NAT) on our LAN.
Many hours later we discovered what the issue was! (Browsing was fine but it would not route inbound traffic. We entered those in the Router's 'WAN IP Network Settings'. The installing tech had given us our IP Address, its Subnet Mask and the Gateway to use, and the DNS Servers. In the Gateway scenario that must be changed to be fixed - and must be your static IP address. Previously the router WAN had been set to be DHCP from the modem. The above was the only setting change that was actually needed). (there were lots of red herrings about the Gateway IP address of 10.1.10.1, etc. Disable all rules and allow all inbound traffic through. Part One - in the Comcast SMC Business Gateway settings. The solution was in two parts - the Comcast people were very helpful indeed and as others have said in this thread we did not actually need them to do anything. We wanted the Gateway to pass all traffic forward to our Router. We upgraded to a Business Gateway with a fixed IP address - and couldn't route. Our situation was that we previously had a wired LAN connected via a Router to a Comcast Modem.
I spent a long time sorting this out - some with Comcast and some digging.