Contributor
•
83 Messages
Delayed Ethernet Connection--more
This follows up on previous conversations about computers with ethernet connections (not wireless) experiencing delays in getting connected after waking up from sleep. People with both the XB6 and XB7 gateways have been experiencing this problem since mid-December.
If you were contributing to the previous discussion about this, please check in here and let's continue the discussion. Here is a partial list participants:
@alantrainor1 , @BlackTriad , @Kruunk83 , @TomasNieve , @sjwj , @hjens , @blueaid
@g-hodgson , @fiero44 , @badcrab
@BlackTriad -- Is your gateway still running the updated firmware? Has the updated firmware fixed your problem?
Has anyone else received updated firmware which has fixed this problem?
corgi11
Problem Solver
•
982 Messages
4 years ago
Comcast has just downloaded an earlier version of software for my xb6 and now the problem is back.
This is what they downloaded today and it has the delay:
0
SteveWW
Contributor
•
83 Messages
4 years ago
@corgi11-- that's unfortunate!
It appears that Comcast does routine scans of gateways and those scans force every unit to be on the designated "released version" of firmware, even though a unit may already be on a later (and bug-free) release that has not yet been granted "released version" status.
This happened to another person here who (via a Comcast tech) received a new version of firmware which fixed the problem... then his firmware was downgraded to the old version that same night and of course the problem returned just as yours did.
Perhaps you can call tech support and ask them to re-push the good version to you. If you are able to get that done, I've seen someone refer to an "exception list" which--if you can get on it--may prevent your unit from going through the downgrade you just experienced.
0
corgi11
Problem Solver
•
982 Messages
4 years ago
It is amazing to me that so few people are responding to this problem. Amazon has sold out of all the unmanaged switches that were mentioned in these threads and they raised the prices of all the other ones. I am a senior with underlying medical conditions and I will not go into a Comcast store for this problem. I won't mail order one because it is a crapshoot on which unit you will get. So as many others have done I bought the last 5 port Netgear unmanged switch that Amazon had for a reasonablr price. I would assume any unmanaged Gigabyte switch would work.
There seems to be a lot of people out there with this problem only they are not responding on this thread.
Comcast keeps closing these threads but the problem still persists. Could someone from Comcast tell us why these threads are being closed?
0
XfinityBillie
Official Employee
•
3.3K Messages
4 years ago
0
g-hodgson
Contributor
•
257 Messages
4 years ago
Just so you know, there were two previous, extensive threads on this issue. Both were locked by someone, and we assumed it was Comcast. Do you have volunteers who help you monitor these threads? Folks who have the permission to lock them? If so, maybe someone needs a little training
Yes, at times some frustrations spilled out into the comments, but I hope you can understand why - especially on a problem that is now 2 months old. But nothing was said that warranted the shutting down of the conversation.
To make matters worse, we never received any notifications/posts (whether via the public threads or via private message) as to why the threads were locked down. They were just abruptly shut down, so we had to restart the conversation twice and try to reach out to all the previous posters. Very frustrating and not very cool.
Anyway, thanks for assuring us that this thread will stay open until there's a resolution. If this thread gets locked, we will reach out to you in a private message to get it unlocked!
Greg
0
hjens
Contributor
•
31 Messages
4 years ago
I am one of the original posters on this thread and others whose Ethernit connectivity time lag problem was solved with a vist to the Comcast store and switching from an XB6 modem to an XB7. But I live in fear of it returning with some firmware update pushed into my system at 3:30 a.m. I'd like to see this addressed ASAP where the problem originated, namely Comcast, never to rear its ugly head again.
0
FlushDNS
New Poster
•
2 Messages
4 years ago
I'm also experiencing this problem.
CGM4331COM
CGM4331COM_4.6p2s1_PROD_sey
0
0
fiero44
Contributor
•
24 Messages
4 years ago
Good morning Steve . Just wanted to pass along some info I received last night . I got a PM from ComcastMarcos wanting to run some diagnostics with me to determine if he could solve the lag problem. I kindly advised him to read the numerous posts as to the nature and origin of the problem and that it appears that a ticket has been generated regarding this . He PM'd back and said he could find no ticket regarding my trouble and wanted to perform tests. A few hours later I got a PM from ComcasrChe that stated, and I'm paraphrasing here, that each person having this problem will need to assist in testing to verify the problem before they can be added to a repair ticket ... Interesting
0
SteveWW
Contributor
•
83 Messages
4 years ago
a) Hello @FlushDNS -- thanks for checking in here. We have many XB7 users here with this problem and all of them have the same firmware version you have. All indications are that this problem relates to a firmware bug and it will take a firmware revision to fix the problem.
If you scroll back a few posts, @ComcastBillie wrote:
If you have not done so already please be sure to send us a private message for further assistance/investigation, along with getting your account linked to the advanced repair ticket created. You can send us a private message by clicking on my hand, "ComcastBillie".
I'd encourage you to do that so that as many people as possible are "on the record" (directly with tech support and not just here in this forum) as having this problem.
b) Also, with reference to "tickets" (and today's post from @fiero44)...
After a series of private message exchanges with various Comcast folks, I was told that my ticket number is CR946158395 . I don't know if that is a ticket personally assigned to me or if it is a general ticket number for this problem. I also don't know whether this ticket was recently created or if it was created some time ago (along with many others here, I've been actively involved with this problem since mid-December).
--> In any case, I would encourage everyone here to refer to this ticket # CR946158395 in any interactions with Comcast about this issue. Even if this ticket is only supposed to apply to me, at least the Comcast rep will see that this problem has already been reported and new reports can piggy-back onto this ticket.
--Steve
0
Kruunk83
Contributor
•
13 Messages
4 years ago
0
Kruunk83
Contributor
•
13 Messages
4 years ago
0
SteveWW
Contributor
•
83 Messages
4 years ago
@Kruunk83-- glad to hear that the problem has been fixed for you. You are at least the second person here who saw the problem fixed when your XB7 firmware was upgraded from 4.6p2s1 to 4.6p5s1. Let's hope that Comcast quickly updates all the the XB7's to 4.6p5s1 as soon as possible.
Likewise, we've seen a report here that on the XB6 gateway, firmware version 4.6p7s1 solves this problem. Let's hope that this version gets widely distributed quickly. With an XB6, I am anxiously waiting for this.
Let's go Comcast!
0
FlushDNS
New Poster
•
2 Messages
4 years ago
I wonder when the rest of us can expect this firmware update?
0
g-hodgson
Contributor
•
257 Messages
4 years ago
0
0
jmah20
Frequent Visitor
•
13 Messages
4 years ago
I’m curious if they even tried to duplicate this problem in-house running the XB7 on 4.6p2s1 firmware??
0
0