Delayed Ethernet Connection

Just recently received the XB6-T (CGM4140COM) from comcast one week ago as my old gateway was starting to fail.

I noticed this immediately after setting it up and finally decided to google the issue and it led me to this thread.

If it's useful information at all, I am using a desktop PC connected directly to the ethernet port on the gateway. After booting my PC the network will be unable to connect for roughing 15 seconds like previously mentioned. It will then connect and work normally. I also want to note that this is happening regardless of complete shut down, sleep, restart, etc. 

The firmware my gateway is running is CGM4140COM_4.4p5s6_PROD_sey

Hello badcrab,

Sorry to hear that you have this problem. But since you do, thanks for checking in here. The more people who report this problem, the more likely it is that we will be able to get it fixed.

I suggest that you scroll back in this thread to a Dec 22nd post from ComcastAmira. Please send her a direct message to let her know that you have this problem. She is interacting with the Comcast support people on our behalf.

It's particularly interesting that you have an XB7 gateway and are having this problem. At least one person posted here that his problem went away when he moved from an XB6 to an XB7. As far as I know, the rest of us here have an XB6. Perhaps it's not a tactical solution for us to switch to an XB7, based on your experience.

Hello blueaid,

Welcome to our "club."

Please see my post just prior to yours in which I suggested to a previous poster that he send a direct message to ComcastAmira.  The more direct reports they get, the sooner we'll get this fixed.

This is clearly affecting a lot of people-- it's just a matter of how long it takes people to find this thread.

Hello @SteveWW, @badcrab, and @blueaid! We appreciate you all for using the Xfinity Forum to report the issues you're having with the delayed ethernet connection, share the troubleshooting steps you have completed, and bounce ideas off of one another. We know how much of an inconvenience this can be for you and want to make sure we can address each of your concerns to help get this fixed. I agree the more users that report this, the sooner we can get it fixed. We're gathering notes of the situations we have run across to communicate them to the Advanced Techs and engineers. I wanted to know if you guys can review this link to see if the Windows 10 Network Settings for Xfinity Internet are configured correctly? Are the Windows 10 and Windows 8 devices being used, running in Desktop mode? Before we reach out to the Advanced Techs, can you review the Xfinity Stream Portal Minimum System Requirements? I know this is something the Advanced Techs may want to verify. 

We ask that you please refrain from sending private messages unless you're asked to. By sending unsolicited private messages to our Official Employees, you are inadvertently violating forums guidelines. Instead, @blueaid, and @badcrab, we ask that you create your own public posts (without your account information)  with details of the issue or experience you're having. Doing so will auto-generate a help ticket in our system. Once that's done, we can assist you in the order your request was received. 

Perfect response, Steve. Better than my rant...lol.

That's fine, Che. I started this thread. I appreciate that you all have your protocols. Just get it fixed.

@ComcastChe wrote:

<< I wanted to know if you guys can review this link to see if the Windows 10 Network Settings for Xfinity Internet are configured correctly? Are the Windows 10 and Windows 8 devices being used, running in Desktop mode? Before we reach out to the Advanced Techs, can you review the Xfinity Stream Portal Minimum System Requirements? I know this is something the Advanced Techs may want to verify. >>

Please do not waste our time. All of us who have posted have been using Comcast internet for some period of time (1.5 years in my case; much longer for some others here) and we never had this problem before. This problem started around the middle of December.  We did not change any internet settings.

We all have cabled ethernet connections to the gateway. In some instances (mine for example), there are two PC's, each connected with its own cable. Everyone who has posted here has found that after waking a computer from sleep, or a fresh re-start, it takes 30 to 35 seconds to get online. This never used to happen. Most of us have the XB6 gateway but one of today's new posters has an XB7.

Most of us have already done all the obvious troubleshooting. Our Win 10 systems are fully updated; we've rebooted; we've restarted the gateway; etc.  The problem persists and more people are posting about this each day, as they find this forum.

Some of us (including me) are computer professionals with extensive experience in the field. At least one other poster is a networking professional. Please don't waste our time by treating us as ignorant.

Comcast changed something around mid-December to cause this problem. Was new firmware pushed out to our gateways? Was a change made at Comcast's end with respect to how internet connections are made and IP leases retained or released? Were any other changes made?

Please check your change logs starting around 12/10/20 and for the next 10 days or so-- the problem will be found within those change logs.

Hey @g-hodgson, thanks for your feedback, and sorry if I offended you in any way. We know that you guys are all trying to help us get the issue resolved, and as I mentioned, we truly appreciate it. This is the type of support we need from you all. It's fine that you all continue to chat and banter here to update one another. That's not an issue. However, due to an update with our systems and making sure the other customers who have commented on your post have a help ticket generated like one was created for you, this is why I have asked them to open their own posts. This is also a rule in our guidelines. I'm not saying we can't help. I'm also trying to make sure we have all the information that the Advanced Techs may ask for to help save more time as we communicate your issues with them. I hope I was able to clarify the reasons behind my request. 

Furthermore, I've been a customer for 30+ years at the same location. I've lived through the growing pains of your acquistions of local cable companies. Also lived through your entry into broadband. For over a year it was an abomination, fighting with you guys weekly.

Service has essentially been good for the last couple of years. But I'm now sitting here, paying for a 1G plan, and getting 35 Mbps at the gateway. Not to mention the original problem, which is the delay connecting to the internet.

Just so you know, I do have another option in my area. Verizon. I've resisted the temptation,

Take that for what it's worth to you.

I understand, @SteveWW, which was not my intention, and I'm sorry you feel this way. I hope we're able to gather as much information as possible, including information that the Advanced Techs may ask down the line. Having this information readily available for them helps save time, so we don't have to keep coming back to your private messages to gather the additional info. To answer your questions, I took a moment to look at your private message to verify your current firmware. Upon further review, I confirmed your modem's firmware is up to date. It was just updated yesterday. I don't think the firmware is going to be the issue. But these things are good for the Advanced techs to know so they can save time searching. There were no other changes made on our end that we are aware of.

I run a Mac connected by Ethernet to my Comcast internet. For the past couple of weeks or so I've been frustrated by a 1-2 minute time lag connecting to the internet. Looking at Network in my system preferences, I first get a message saying I do not have an IP address. Then I get a message saying my IP address is self-assigned and cannot be connected. Then I am finally connected with a green light next to my ethernet connection. The process takes 1-2 minutes. Never happened in the past. What gives?

Exactly right, blueaid.

@ComcastChe I understand what you are saying, it's just that @ComcastAmira quite literally told us to speficially direct message them our issues so they could be passed along.