Very interesting thread by ctontar. Like him I run a Mac (OS Catalina) but my delayed Ethernet connection via Comcast's internet service started in mid-December with the XB6-T Technicolor modem. As soon as I upgraded to the XB7-T it solved the problem. The model number on my new modem, as listed on the receipt, was Model 37. I never could find that model number on the modem itself but since it solved the problem I never bothered to go into it further. If there are now two users with XB7 problems, I wonder if it's a model problem or speed related to local signal strength. Because of Covid-19 a lot of people are working online these days putting strains on the ISP?
Sounds like commenter badcrab may have already had the Technicolor XB7 prior to mid December, when us Technicolor XB6 users started having this problem?
And not sure when ctontar switched from the XB6 (which wasn't having the delay issue) to the XB7 (which has the delay issue).
If both of them had their XB7s prior to the firmware push that caused the problem for all of us XB6 users, then they received that push too - so they now also have the problem.
And like Steve alluded to in the original thread: The XB7s those of us got from Comcast over the last week or so are likely loaded with the earlier firmware code, which didn't have the problem. That's why our XB7s solved the problem...older code.
If I'm right, I'm hoping Comcast is working on code to correct this issue (along with undoubtedly other issues) in the next firmware release/push.
In other words: Comcast, don't push any firmware releases until this problem is resolved!Otherwise, you will cause us new XB7 users the same problem we had with the XB6!
As for speed: I was running almost 1 Gbps on my XB6 when this problem started. But you are right, in that Comcast had put a max cap speed in some areas because of the current high demand. Folks working from home, but aso all the kids virtually attending school at home. They did it in my area for about a week, but they've since resolved that problem and I'm now back to full speed.
Several days ago Greg posted a link to a post in a Windows forum which talked about this issue. Here is the essence of that person's analysis:
<< My computer is showing a 3-day lease period. (Windows Command > IPConfig /all)
In other words, my computer, via the router (XB6 Gateway) is assigned a dynamic IP Address from the DHCP Server for temporary use -- at least for 3 days. If I put my computer to sleep to go out for a few hours, then when I return and wake the computer from sleep, it should be using the same IP Address as before.
But what appears to be happening is that the DHCP Server (or XB6) thinks that my lease has expired, and that my computer needs a new dynamic IP Address. And that process of assigning a new IP Address is taking about 30 seconds to do.
It's as if the XB6 is ignoring renewal requests, misunderstanding the lease status, or resetting something... >>
That seems to me to be a reasonable hypothesis as to what is happening. The question is, "Why is it happening?"
I've previously speculated that this change in behavior may be due to one or more firmware updates that have been pushed out to the gateways. Several people have moved to XB7 gateways and have seen the problem disappear, although there are a couple of anomolous data points in which a few XB7 users also have this problem. I think it would be helpful to know which firmware versions are currently running on the XB7. Specifically:
--> If you used to have this problem, moved to the XB7 and currently do not have this problem, could you make note of your current XB7 firmware revision and post it to this thread?
--> If you currently do have this slow connection problem on an XB7 it would be helpful if you also would post your firmware revision.
Also, please make note of whether your XB7 gateway was manufactured by Technicolor (CGM4331COM) or Arris (TG4482A).
This will provide important baseline information. If the problem does start showing up on recently installed XB7's this data will be helpful in assessing whether or not a firmware change is implicated. Likewise, it will be interesting to see if XB7's with and without this problem are running different firmware versions.
Thanks.
--Steve
For historical reference: I'm still on XB6 and still having this problem
That sounds like a great way of finally isolating the issue.
Only problem is I'm not sure how to find the firmware version I currently have. I'd appreciate it if someone could help instruct me as to how to find the firmare version?
<< Only problem is I'm not sure how to find the firmware version I currently have. I'd appreciate it if someone could help instruct me as to how to find the firmare version? >>
One way is to log into your gateway at 10.0.0.1 -- in the column at the left, click on "Software"
The text next to "Software Image Name" is the firmware version.
Thanks to those who have already posted their firmware revisions. I'm compiling all that into a database for ongoing reference. I've been through the original thread relating to this problem and the previous postings in the current thread and I've captured the firmware info that was previously posted.
All firmware entries are welcome but particularly important right now will be to capture the firmware revision #'s for people who have XB7's and are not experiencing the slow connection problem, as well as anyone who has an XB7 that does have the problem.
If these firmware revisions change and those changes are associated with a status change of this problem, that will be worth knowing.
I do not have the exact date that I received the XBT-7 but it was in early October (!). The delay problem started as soon as I received the XBT-7 and had not occurred when I had the XBT-6. It was a bit strange the way I received the XBT-7. My service wires to the street had blown down and a technician from Xfinity came out to repair it and said that he could update the router while there.
So, it seems that I have had this problem much earlier than most. I tried once through the Xfinity Assistant to see if I could end the delay issue but the experience was not positive.
Again, the XBT-7 is model cgm4331com. The Firmware is CGM4331COM_4.6P2s1_PROD_sey
Just checking in to add some information requested by Steve. I appreciate your work compiling this data.
This issue occurs when the nodes' NICs are set to manual/static internal IPs, too. Nov 15 2020 was my install date and the date I received my modem. New Coax run. Property vacant and modem went unused almost a month but noticed issue immediately upon use. Device: CGM4331COM (XB7) Technicolor Firmware: CGM4331COM_4.6p2s1_PROD_sey
Based on limited data received so far, I can make these observations:
a) XB7:
Two people (ctontar and badcrab) have XB7's which do exhibit this problem. Both have the model made by Technicolor and have the same firmware (4.6p2s1).
g-hodgson has an XB7 which does not have the problem. His unit is made by Arris.
I know that others have previously posted that their XB7's do not have the problem and I think-- but I'm not certain-- that they have the Technicolor model. They haven't yet posted their firmware versions. I hope we get to see that. Right now this information is too limited to draw firm conclusions.
b) XB6's which have this problem:
Most people the same firmware: 4.4p6s1
However, bluaid has what appears to be an older version: 4.4p5s6
And corgi11 appears to have a newer version: 4.6p3s2
Again, the data is limited but this seems to suggest that if this problem is due to a firmware issue, then it may have originated in version 4.4p5s6 or earlier. (Although my personal suspicion is that it's a firmware issue, that's not a certainty.)
I don't think any of us know how frequently Comcast pushes out firmware updates and we don't know how long our gateways have had the firmware version they currently have. But at least now we are aware of the version we have so we can check to see if there has been a firmware change if we see a behavioral change.
A little while ago I received a private message from ComcastGina. She expressed appreciation for all the debugging work that's been done by us and empathy for the problem we've been dealing with. She said she would take the needed steps to be certain that this problem received attention and resolution. I conveyed my thanks and my appreciation for her support but I also pointed out that we had received similar commitments before (from other Comcast employees) and that those commitments had not been met. I expressed hope that we would not be disappointed again. I asked that she keep us informed by posting to the thread.
So I'm hopeful that something good may happen. Let's hope for the best.
Thanks, Steve. I'm glad a Comcast rep has reached out to you. The last time that happened, we ended up with a locked thread and several reps leaving us high and dry.
Mac user here running Catalina OS. Don't know the software of my old XB6-T modem which started experiencing the Ethernet connection time lag since I traded it in for an XB7-T on Jan. 4. Gateway CGM4331COM Firmware 4.4p12s1_PROD_sey
hjens
Contributor
•
31 Messages
4 years ago
Very interesting thread by ctontar. Like him I run a Mac (OS Catalina) but my delayed Ethernet connection via Comcast's internet service started in mid-December with the XB6-T Technicolor modem. As soon as I upgraded to the XB7-T it solved the problem. The model number on my new modem, as listed on the receipt, was Model 37. I never could find that model number on the modem itself but since it solved the problem I never bothered to go into it further. If there are now two users with XB7 problems, I wonder if it's a model problem or speed related to local signal strength. Because of Covid-19 a lot of people are working online these days putting strains on the ISP?
0
g-hodgson
Contributor
•
257 Messages
4 years ago
Sounds like commenter badcrab may have already had the Technicolor XB7 prior to mid December, when us Technicolor XB6 users started having this problem?
And not sure when ctontar switched from the XB6 (which wasn't having the delay issue) to the XB7 (which has the delay issue).
If both of them had their XB7s prior to the firmware push that caused the problem for all of us XB6 users, then they received that push too - so they now also have the problem.
And like Steve alluded to in the original thread: The XB7s those of us got from Comcast over the last week or so are likely loaded with the earlier firmware code, which didn't have the problem. That's why our XB7s solved the problem...older code.
If I'm right, I'm hoping Comcast is working on code to correct this issue (along with undoubtedly other issues) in the next firmware release/push.
In other words: Comcast, don't push any firmware releases until this problem is resolved! Otherwise, you will cause us new XB7 users the same problem we had with the XB6!
As for speed: I was running almost 1 Gbps on my XB6 when this problem started. But you are right, in that Comcast had put a max cap speed in some areas because of the current high demand. Folks working from home, but aso all the kids virtually attending school at home. They did it in my area for about a week, but they've since resolved that problem and I'm now back to full speed.
0
SteveWW
Contributor
•
83 Messages
4 years ago
Several days ago Greg posted a link to a post in a Windows forum which talked about this issue. Here is the essence of that person's analysis:
<< My computer is showing a 3-day lease period. (Windows Command > IPConfig /all)
In other words, my computer, via the router (XB6 Gateway) is assigned a dynamic IP Address from the DHCP Server for temporary use -- at least for 3 days. If I put my computer to sleep to go out for a few hours, then when I return and wake the computer from sleep, it should be using the same IP Address as before.
But what appears to be happening is that the DHCP Server (or XB6) thinks that my lease has expired, and that my computer needs a new dynamic IP Address. And that process of assigning a new IP Address is taking about 30 seconds to do.
It's as if the XB6 is ignoring renewal requests, misunderstanding the lease status, or resetting something... >>
That seems to me to be a reasonable hypothesis as to what is happening. The question is, "Why is it happening?"
I've previously speculated that this change in behavior may be due to one or more firmware updates that have been pushed out to the gateways. Several people have moved to XB7 gateways and have seen the problem disappear, although there are a couple of anomolous data points in which a few XB7 users also have this problem. I think it would be helpful to know which firmware versions are currently running on the XB7. Specifically:
--> If you used to have this problem, moved to the XB7 and currently do not have this problem, could you make note of your current XB7 firmware revision and post it to this thread?
--> If you currently do have this slow connection problem on an XB7 it would be helpful if you also would post your firmware revision.
Also, please make note of whether your XB7 gateway was manufactured by Technicolor (CGM4331COM) or Arris (TG4482A).
This will provide important baseline information. If the problem does start showing up on recently installed XB7's this data will be helpful in assessing whether or not a firmware change is implicated. Likewise, it will be interesting to see if XB7's with and without this problem are running different firmware versions.
Thanks.
--Steve
For historical reference: I'm still on XB6 and still having this problem
Firmware: CGM4140COM_4.4p6s1_PROD_sey
0
alantrainor1
Frequent Visitor
•
13 Messages
4 years ago
That sounds like a great way of finally isolating the issue.
Only problem is I'm not sure how to find the firmware version I currently have. I'd appreciate it if someone could help instruct me as to how to find the firmare version?
0
SteveWW
Contributor
•
83 Messages
4 years ago
<< Only problem is I'm not sure how to find the firmware version I currently have. I'd appreciate it if someone could help instruct me as to how to find the firmare version? >>
One way is to log into your gateway at 10.0.0.1 -- in the column at the left, click on "Software"
The text next to "Software Image Name" is the firmware version.
--Steve
0
g-hodgson
Contributor
•
257 Messages
4 years ago
I didn't know how to find the f/w version either. Steve helped out. Two ways he showed us. Here's from his older post:
To find the firmware version:
1. Login to your router at 10.0.0.1
2. About half-way down the column on the left, click on Software
3. Software Image Name is the firmware revision
Another way to do this:
1. Go to my.xfinity.com
2. Log into your xfinity account if not already logged in
3. In the bar near the top of the page, click on the graphic for Wireless
4. Click on Connect (to the right of Overview)
5. Click on See Network
6. Click on "Gateway Online"
7. Scroll down and click on Gateway Details
An overlay window will pop up and show you the firmware revision along with other information
As always, thanks Steve.
My Arris XB7 f/w is: TG4482PC2_4.4p17s3_PROD_sey
0
alantrainor1
Frequent Visitor
•
13 Messages
4 years ago
Thanks Steve.
I have the XBT-6. I have the delay issue. I'm running firmware version CGM4140COM_4.4p6s1_PROD_sey
0
g-hodgson
Contributor
•
257 Messages
4 years ago
For reference, my previous Technicolor XB6 firmware was:
COM4140COM_4.4p6s1_PROD_sey
0
0
SteveWW
Contributor
•
83 Messages
4 years ago
Thanks to those who have already posted their firmware revisions. I'm compiling all that into a database for ongoing reference. I've been through the original thread relating to this problem and the previous postings in the current thread and I've captured the firmware info that was previously posted.
All firmware entries are welcome but particularly important right now will be to capture the firmware revision #'s for people who have XB7's and are not experiencing the slow connection problem, as well as anyone who has an XB7 that does have the problem.
If these firmware revisions change and those changes are associated with a status change of this problem, that will be worth knowing.
--Steve
0
ctontar
Regular Visitor
•
3 Messages
4 years ago
I do not have the exact date that I received the XBT-7 but it was in early October (!). The delay problem started as soon as I received the XBT-7 and had not occurred when I had the XBT-6. It was a bit strange the way I received the XBT-7. My service wires to the street had blown down and a technician from Xfinity came out to repair it and said that he could update the router while there.
So, it seems that I have had this problem much earlier than most. I tried once through the Xfinity Assistant to see if I could end the delay issue but the experience was not positive.
Again, the XBT-7 is model cgm4331com. The Firmware is CGM4331COM_4.6P2s1_PROD_sey
0
badcrab
Frequent Visitor
•
7 Messages
4 years ago
Just checking in to add some information requested by Steve. I appreciate your work compiling this data.
This issue occurs when the nodes' NICs are set to manual/static internal IPs, too.
Nov 15 2020 was my install date and the date I received my modem. New Coax run. Property vacant and modem went unused almost a month but noticed issue immediately upon use.
Device: CGM4331COM (XB7) Technicolor
Firmware: CGM4331COM_4.6p2s1_PROD_sey
0
SteveWW
Contributor
•
83 Messages
4 years ago
Based on limited data received so far, I can make these observations:
a) XB7:
Two people (ctontar and badcrab) have XB7's which do exhibit this problem. Both have the model made by Technicolor and have the same firmware (4.6p2s1).
g-hodgson has an XB7 which does not have the problem. His unit is made by Arris.
I know that others have previously posted that their XB7's do not have the problem and I think-- but I'm not certain-- that they have the Technicolor model. They haven't yet posted their firmware versions. I hope we get to see that. Right now this information is too limited to draw firm conclusions.
b) XB6's which have this problem:
Most people the same firmware: 4.4p6s1
However, bluaid has what appears to be an older version: 4.4p5s6
And corgi11 appears to have a newer version: 4.6p3s2
Again, the data is limited but this seems to suggest that if this problem is due to a firmware issue, then it may have originated in version 4.4p5s6 or earlier. (Although my personal suspicion is that it's a firmware issue, that's not a certainty.)
I don't think any of us know how frequently Comcast pushes out firmware updates and we don't know how long our gateways have had the firmware version they currently have. But at least now we are aware of the version we have so we can check to see if there has been a firmware change if we see a behavioral change.
--Steve
0
SteveWW
Contributor
•
83 Messages
4 years ago
A little while ago I received a private message from ComcastGina. She expressed appreciation for all the debugging work that's been done by us and empathy for the problem we've been dealing with. She said she would take the needed steps to be certain that this problem received attention and resolution. I conveyed my thanks and my appreciation for her support but I also pointed out that we had received similar commitments before (from other Comcast employees) and that those commitments had not been met. I expressed hope that we would not be disappointed again. I asked that she keep us informed by posting to the thread.
So I'm hopeful that something good may happen. Let's hope for the best.
0
g-hodgson
Contributor
•
257 Messages
4 years ago
Let's hope for a better outcome this time.
0
hjens
Contributor
•
31 Messages
4 years ago
Mac user here running Catalina OS. Don't know the software of my old XB6-T modem which started experiencing the Ethernet connection time lag since I traded it in for an XB7-T on Jan. 4. Gateway CGM4331COM Firmware 4.4p12s1_PROD_sey
0