DHCP to Static issues, and cannot manage modem

Hi LG_SK and welcome to the business forums.

I can certainly review your network issues. I have also included a link for logging into the admin tool of the gateway. Please private message me your full name, the name of your business, the full service address and the phone number associated with your account.

https://business.comcast.com/help-and-support/internet/setup-manage-comcast-wifi-business-wireless-gateway/

I can also look into the ticket as well. Please private message me your full name, the name of your business, the full service address and the phone number associated with your account.

Update: online chat help indicated that a tier 2 rep has had it "parked" for quite some time, so that may explain why I cannot manage my own router. Would have been nice to know this when they parked it.

This is the most plain vanilla, set up a new router, add a few static IPs and let the rest be DHCP. Simple. Most basic thing a custmer can have.

But somehow Comcast has managed to keep static and DHCP clients from effectively talking to each other. 

No call backs for days. No ability for me to manage the device. Comcast will not let me use my own modem.

Three days and no solution, but worse nobody calls, even when I am told "somebody will call you tomorrow." Even then they say "OK, sorry about nobody calling yesterday, somebody will call you today."

This is routing 101, and Comcast doesn't want to get back to the client who has been paying them over $200 each month for many years.

Edit: Management of the router from a static IP takes about a minute to sign in or get from screen to screen. Maybe this is considered normal.

When connecting to a database from over 100 miles away is much faster than connecting within the office, there is a problem.

Each time I am speaking to someone who is new to the issue, and I have to start over. No, Comcast worker, this is NOT a problem with devices acquiring an address. This is NOT an issue of new equipment (there is none.) This is NOT an issue of cables or power. This is NOT a DHCP issue. Same equipment with updated cables just to be sure. I've been though all that, and several times because each call is like starting over.

This IS an issue of communication between devices within the office., specifically DHCP to static, even when both are connected directly to your special-issue cable modem. Even when the only two connections on the entire network are one static and one DHCP. PIngs of 200ms with one hop is not acceptible, but we will take that over the constantly dropped pings.

I know generally where the problem is, and they are going to replace the new cable modem with the same model, and if all settings are the same on the new modem then the issue will most likely persist. How will I know if the settings are the same? I will never know.

I will drive 2 hours to the site for a third time in one week. Hopefully I will not be watching as the same model modem is installed with the same settings, and the workers in the office asking if they should head to the local McDonalds to get a faster connection to the server sitting right beside them.

I am experiencing a very similar issue.

I have Comcast Business Internet with a block of 13 static ips.  Because my home office has way more than 13 devices, the large majority of our devices are using DHCP and therefore assigned 10.1.10.* addresses, and only a handful of devices, the ones that need public ips, are assigned one of the coveted 13 static ips in the 173.x.x.x range.

My issue is that there is some sort of weird routing issue between devices on my network with 10.1.10.* addresses and ones with the public 173.x.x.x addresses.  In fact, if I'm on my Mac laptop with a 10.1.10.* address, and I try to ssh to one of my devices with a 173.x.x.x address, it never works unless I first do a ping before the ssh.  Isn't that strange?  After I do a ping, the ssh will work for while, but will stop working soon after unless I do another ping again.  Very odd behavior.  I should also note that pings between 10.1.10.* devices and 173.x.x.x. devices always start slow (10-100ms), then after the first few pings, settle down to 2ms range.  

Please help, as it's really a pain to have to keep issuing pings to keep ssh working.

I should add that I have a Cisco DPC3941B modem and that whenever I login to my modem at 10.1.10.1, I can manage the modem, but it responds very slowly.  It's as if the modem is getting really taxed.  

Hi alexpoon. I just responded to your private message. Please send a reply there.