The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.
SMC Comcast Business Router Configuration
There are a number of other posts with similar questions, but none that I found were able to help me.
When you get a business line from Comcast they give you an SMC router/firewall/modem. Before switching to Comcast business, we had a SonicWall firewall configured and working perfectly for our previous ISP. It allowed inbound terminal services to our terminal services server and OWA (http/https) connections to our exchange server.
Now that I have to place this SMC router in front of the firewall, I'm in a situation where getting the double NAT'ed firewalls working is not as simple as I had hoped.
I know the setup below is wrong because although I have internet access from behind the SonicWall, I can't get in from the outside using services that previously worked (OWA and terminal services).
Comcast wrote down two IPs on the work order:
IP#1: 173.xxx.xxx.205/24
IP#2: 173.xxx.xxx.206/30
Gateway: 10.1.10.1
So this is my setup on the SonicWall:
WAN: NAT-Enabled Static IP: 173.xxx.xxx.205/24
Gateway: 10.1.10.1
SMC:
LAN IP: 10.1.10.1/24
WAN IP: 173.xxx.xxx.206
Static IP Block 173.xxx.xxx.206/30
"Firewall for True Static IP Subnet Only" disabled
"Gateway Smart Packet Detection" disabled
"Static Routing" disabled
"Port Forwarding" disabled
"1 to 1 NAT" disabled
173.xxx.xxx.205 is in the DMZ (I was trying to achieve a "bridge-like" mode even though this device doesn't have a bridge mode)
When I check my public IP from behind the SonicWall, it's currently 173.xxx.xxx.205
What do I need to change for this to work properly?
When you get a business line from Comcast they give you an SMC router/firewall/modem. Before switching to Comcast business, we had a SonicWall firewall configured and working perfectly for our previous ISP. It allowed inbound terminal services to our terminal services server and OWA (http/https) connections to our exchange server.
Now that I have to place this SMC router in front of the firewall, I'm in a situation where getting the double NAT'ed firewalls working is not as simple as I had hoped.
I know the setup below is wrong because although I have internet access from behind the SonicWall, I can't get in from the outside using services that previously worked (OWA and terminal services).
Comcast wrote down two IPs on the work order:
IP#1: 173.xxx.xxx.205/24
IP#2: 173.xxx.xxx.206/30
Gateway: 10.1.10.1
So this is my setup on the SonicWall:
WAN: NAT-Enabled Static IP: 173.xxx.xxx.205/24
Gateway: 10.1.10.1
SMC:
LAN IP: 10.1.10.1/24
WAN IP: 173.xxx.xxx.206
Static IP Block 173.xxx.xxx.206/30
"Firewall for True Static IP Subnet Only" disabled
"Gateway Smart Packet Detection" disabled
"Static Routing" disabled
"Port Forwarding" disabled
"1 to 1 NAT" disabled
173.xxx.xxx.205 is in the DMZ (I was trying to achieve a "bridge-like" mode even though this device doesn't have a bridge mode)
When I check my public IP from behind the SonicWall, it's currently 173.xxx.xxx.205
What do I need to change for this to work properly?
Asked:
Who is Participating?
Experts Exchange Solution brought to you by
Enjoy your complimentary solution view.
Get every solution instantly with Premium.
Start your 7-day free trial.
I wear a lot of hats...
"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.
Experts Exchange Solution brought to you by
Your issues matter to us.
Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.
Start your 7-day free trial
Well the smc gateway has an ip of .206, I;m supposed to be using the .205 address, as we've paid for a static IP.
The SMC does have ethernet ports on it - 4 to be exact. If I configure the SonicWall's WAN IP as the .205 IP, what do I use as the gateway?
The SMC does have ethernet ports on it - 4 to be exact. If I configure the SonicWall's WAN IP as the .205 IP, what do I use as the gateway?
Use the .206 as the gateway. This gateway is not for the SMC device but your ISP's gateway for the internet.
Connect your Sonicwall unit to the etheret port located on the SMC device.
Connect your Sonicwall unit to the etheret port located on the SMC device.
One major Issue:
The part that your sonicWall has a WAN ip of 173.xxx and a Gateway of 10.1.10.1 is wrong. You can never have that. Meaning the Gateway and IP of the device have to be on the same network.
Issue Number 2: you mentioned that:
173.xxx.xxx.205 is in the DMZ (I was trying to achieve a "bridge-like" mode even though this device doesn't have a bridge mode) and 1 to 1 NAT" disabled
So what is your internal IP address of sonic wall? How does it communicate with the gateway you provided? Like I said they have to be on the same network for them to talk to each other. there needs to be some sort of a translation or NATing. (your issue number 2)
I just gave you list of things that are wrong but I have not provided any solution. So answer these questions so I can give you some more help. Which device acts as the DHCP server? Which device does the NATing? May be you can disable the NAT on your SMC device and make it act like a layer 2 bridge (roughly).
Let me know
The part that your sonicWall has a WAN ip of 173.xxx and a Gateway of 10.1.10.1 is wrong. You can never have that. Meaning the Gateway and IP of the device have to be on the same network.
Issue Number 2: you mentioned that:
173.xxx.xxx.205 is in the DMZ (I was trying to achieve a "bridge-like" mode even though this device doesn't have a bridge mode) and 1 to 1 NAT" disabled
So what is your internal IP address of sonic wall? How does it communicate with the gateway you provided? Like I said they have to be on the same network for them to talk to each other. there needs to be some sort of a translation or NATing. (your issue number 2)
I just gave you list of things that are wrong but I have not provided any solution. So answer these questions so I can give you some more help. Which device acts as the DHCP server? Which device does the NATing? May be you can disable the NAT on your SMC device and make it act like a layer 2 bridge (roughly).
Let me know
Setting the WAN IP on the firewall to .205 and using .206 as the gateway (the smc device), I was able to get an internet connection working with .205 as my public IP. My internal addresses behind the firewall are using 192.168.40.x, but that doesn't seem relevant. Everything seems to be working now.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Broadband
From novice to tech pro — start learning today.
-
Business CommunicationCertification: PMI RMP Project Management Institute Risk Management… 113 lessons
Experts Exchange Solution brought to you by
Enjoy your complimentary solution view.
Get every solution instantly with Premium.
Start your 7-day free trial.
Does the SMC device have any ethernet ports on it? If so, try configuring your sonicwall with one of the public IPs and connect it to the LAN port on the SMC box.