Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

General discussion

Can't Post on CNET Forums Using DSL, Dialup Works

Apr 24, 2012 6:26AM PDT

I've encountered a very unusual situation and wonder if anyone has any suggestions.

Recently I have not been able to post on the CNET Forums and get red text saying the following:

"Sorry, there was a problem submitting your post. Please try again"

This happens with both Firefox and Internet Explorer. Everything worked fine two months ago. The Preview works normally. The system is a PC running WinXP. I booted Ubuntu Linux from a CD and Flash Drive and get the exact same results.

I have deleted cookies, reset the modem, logged in and out, and repeated the attempt to post for many days. My IP address is different every day.

I then tried a 56K modem and the Dialup Connection works with CNET! It would appear that the DSL is somehow at fault. The DSL and Dialup are both provided by AT&T.

However, this computer works fine on many forums and secure web sites.

I've turned the DSL Modem off and on and run Speed Tests. All appears normal. I also accessed the Speedstream DSL modem directly with the web address provided on the bottom label and all diagnostics pass.

If anyone has any suggestions, please pass them along. Since I can access many other forums using DSL, I assume CNET is interacting with the user differently compared with other forums.

I am using my Dialup service for this post and will respond when I can.

Discussion is locked

- Collapse -
Glad to see this post
Apr 24, 2012 6:34AM PDT

My apologies for not getting back to you, but I have alerted my colleagues about this post to see if anyone else has any ideas.

Mark

- Collapse -
There is one clue so far. ATT.
Apr 24, 2012 6:58AM PDT

ATT had and probably still has DNS issues. Then we have that DNS hijack issue to consider.

If this was my machine I'd try the Google DNS next. It's noted at
https://developers.google.com/speed/public-dns/docs/using

I'm not going to go down the DNS hijack issue yet for a simple reason which is the Linux CD.
Bob

- Collapse -
Thanks Mark and Bob
Apr 24, 2012 8:17AM PDT

Thanks Mark and Bob. This Dialup connection isn't as difficult to use as I expected. I just turn off the DSL Modem which is followed by a warning about a lost connection, and then double click the icon associated with my 56K modem.

At this end, I think the main variables are the DSL Modem and the DSL Service.

There is something called "RIP & Rebuild" that can be done by the DSL provider. I think a technician must make the request to 2nd Level Support. That process apparently resets and completely rebuilds one's connection to the DSL provider and would involve the hardware and software at their end. I wonder if functionality at their end might be something less than 100% involving some feature used by CNET.

I don't really suspect my DSL modem as all other internet activity works perfectly.

Bob, I'll take a look at the DNS information that you referenced.

Thanks, Kent

- Collapse -
I also have ATT, but Uverse
Apr 24, 2012 10:53AM PDT

not DSL and use ATT DNS servers, without problems. I have McAfee AV and that gives me problems getting to sites sometimes.

- Collapse -
It's an issue I encounter from time to time.
Apr 24, 2012 6:32PM PDT

And it's a mystery to all why it comes and goes as well as works for most but not all.

So it's always on my list.
Bob

- Collapse -
KAWill70, I'm going to email directly and ask you some
Apr 24, 2012 8:39AM PDT

questions.

So look for my email shortly.

Thanks!
-Lee

- Collapse -
DSL Now Working - No Changes Made
Apr 24, 2012 2:31PM PDT

DSL is now working and no changes have been made at this end. This will make it difficult to do much more unless it stops working again.

Earlier today I did a quick test with the Google DNS addresses as suggested by Bob. I was not able to post on CNET but I am not sure if the new addresses were actually active.

Tonight I experimented with those addresses and also some invalid ones and there seems to be a delay before they become active. Either that or one needs to close and open the browser. I was also not sure if I needed addresses for IPv4 or IPv6. The addresses for IPv4 do work and I assume that is what this system uses.

I'm back to using DNS addresses selected automatically and I rebooted the system before writing this post.

Thanks again to Mark, Bob, Lee, and Ed for your help. I'll repeat the tests tomorrow.

Kent

- Collapse -
It's working now?
Apr 24, 2012 8:17PM PDT

Just to be clear, you tested Google DNS, (not something I know much about sadly), and after a bit of trouble you got that to work, and are now able to post and reply in these forums. Is that right?

But now where are we/you? Are you still using Google DNS or did you revert your DNS back to AT&T?

I do hope you are back and working with AT&T as I know this has been a trial for you.

Mark

- Collapse -
Back On Dialup Connection
Apr 25, 2012 5:13AM PDT

Mark,

No, the Google Public DNS did not help. Last night when I was able to post using DSL no changes had been made and suddenly DSL worked. I have no idea why. The IP address was somewhat higher than what I typically get. Today things are different and DSL will not work.

My current IP Address using Dialup is drastically different from what I get using DSL.

This is not a trial of DSL. I've had this service for about 6 years with almost no trouble.

Sorry that my comments on Google Public DNS were confusing. I tried it very quickly initially and it did not help. However, I was not sure at that time whether the new settings were active. I also experimented with invalid addresses just to make sure that nothing worked.

I'm currently using the Google Public DNS addresses and have verified that they work.

So, the bottom line is that I don't know what is causing the CNET Posting Problem when using DSL.

Kent

- Collapse -
I'm going to suggest
Apr 25, 2012 9:37PM PDT

Flush DNS.

But I am hoping others here will say whether that's a good idea or not.

This link shows how to do that;
http://www.howtogeek.com/howto/windows-vista/troubleshoot-browsing-issues-by-reloading-the-dns-client-cache-in-vista/

And this link explains a little of what DNS is and what flushing DNS does;
http://ask-leo.com/how_does_flushing_dns_help_resolve_some_issues_and_while_youre_at_it_whats_dns.html

It doesn't do any harm to do it, but I am just not sure why it would need to be done since you can see the CNET pages anyway.

Mark

- Collapse -
Good idea about flush DNS but arp too.
Apr 26, 2012 2:23AM PDT

But that's a machine thing so a boot to Linux should have that covered.

To me this stinks of the old ATT issues we ran afoul of for Samsung HDTV apps. Something about ATT's DNS. We never got the exact list of servers that Samsung needed access to but Google DNS helped.

-> But there is that other area worth looking at. Ready?

Many new routers/DSL included have a firewall setting. I don't want to go over this again in too much detail except we know to turn it off.
Bob

- Collapse -
Test Using Ubuntu Linux and same DSL Service
Apr 24, 2012 3:11PM PDT

I just booted Ubuntu Linux from a Flash Drive and am running "Live" using memory as the disk.

Previously this configuration would not post on CNET.

In a moment we'll know if this works.

IP Address is 69.233.253.176

Kent

- Collapse -
On Dialup
Apr 26, 2012 6:21AM PDT

Thanks Mark and Bob.

I just flushed the DNS cache using the WinXP Command Prompt Window and received the proper response back. The Browser was closed at that time. Unfortunately, I was not able to post on CNET after flushing the cache.

I wonder if DNS is really suspect since I can Preview the attempted post.

Every day I attempt to Post on the Test Forum to see if DSL works. So far I have only seen things work once over the last several days.

Interestingly, the IP address was higher than what I normally get. I was also able to post using Ubuntu Linux and that post is in this thread. The IP address at that time is shown in the post.

I'm hoping that I'll catch another day when things work and then check the IP address to see if there is any pattern.

It's also interesting that Bob occasionally sees this same problem. For now I'll see if I can gather any additional data from these experiments. If so, I'll use my Dialup Connection and post any information. I'll now shut down the DSL modem and post this note which I am composing offline in Notepad.

Kent

- Collapse -
DSL Working Today
Apr 27, 2012 4:33AM PDT

My IP Address today starts with 69.233 similar to what worked a few days ago.

See my post in this thread via Ubuntu Linux for that IP Address which also worked using WinXP.

When DSL has not worked, my IP Address started with 69.228 or 69.226.

The IP Address when I connect with Dialup always starts with 12.72. Dialup has always worked when posting on CNET.

Can anyone suggest anything based on this information?

Would you suspect my DSL Service, or possibly something at CNET?

Thanks, Kent

- Collapse -
All I can suggest is
Apr 27, 2012 4:53AM PDT

that as AT&T assign IP addresses to your computer, (or modem/router), for your DSL connection each session, that you make the call to AT&T and attempt to explain the problem.

But lets see what others say.

If you do call AT&T then I wish you luck because I doubt the first person you speak to at their call center is going to understand any of it and I suspect you are going to have to ask to speak to a tech. You might ask to be assigned a static IP address, but I understand AT&T only apply those in business cases.

I did see this;
http://forums.att.com/t5/Email-Internet-Security/MY-assigned-IP-address-from-AT-amp-T-keeps-changing-while-I-m/td-p/2019861

It is their forums. The first post doesn't really seem to apply to you, but have a look at the only reply and his list of things that can cause "Sporadic or intermittent loss of your connection". Again, not applicable to your situation, but then at this stage have a look at any cause?

In fact I wonder if you would also want to post your problem in AT&T forums. We don't normally solicit CNET members away from these forums, but in problem specific problems like yours I think that might be a good idea.

Mark

- Collapse -
DSL Working Today
Apr 28, 2012 6:09AM PDT

Mark - Thanks for your most recent reply.. I tried posting on the AT&T Forum yesterday and so far have not received a single reply. That makes me appreciate CNET even more with several moderators joining in on this discussion.

Once again my IP address came up in the range of 69.233.xxx.xxx. This range has worked consistently so far. IP addresses starting with 69.226 or 69.228 always fail to work with CNET.

I also tried Linux again using a 69.228 IP address and it failed to work. Ubuntu has now released the April 2012 version which includes Firefox 11. It took about an hour to download the 700 MB iso file using my AT&T DSL.

It's quite interesting to me that an IP address starting with 69.233 works consistently while 69.226 and 69.228 fail.

Does anyone think this problem could be at the CNET end? There must be some fairly complex code that deals with posting, checking User ID, determining if that user is blocked, and also implementing security to prevent unauthorized posts. I'm sure the problem could also be elsewhere.

Thanks to all, Kent

- Collapse -
It is very strange
Apr 28, 2012 9:52PM PDT

but with your question, 'could this be a problem at CNET's end", I would have to initially say no.

Only because your particular problem is not being seen with anyone else.

Just a thought, probably a wild one, when you are allocated this 69.226 or 69.228 IP address again, visit this site; http://dns-ok.us/

In fact, visit it anyway with the IP address that works, so you can see why.

Do you see an image with a green background and the words, "DNS Resolution = GREEN" if you visit with those strange IP addresses? If so, forget I mentioned it because everything is fine in that respect.

For an explanation, have a read of this discussion; http://forums.cnet.com/7723-7583_102-561604/will-the-internet-end-in-july/?tag=posts;msg5303940 . Carol explains the situation well.

It is a wild thought, I admit.

Mark

- Collapse -
Additional Thoughts
Apr 29, 2012 9:54AM PDT

Mark,

I tried the website you referenced and do get the Green background.

A Google search on the CNET Error Message "Sorry, there was a problem submitting your post. Please try again" does result in some hits.

One apparent cause is a duplicate post. Maybe my posts appear to be duplicates for some reason.

You mentioned that my problem is not being experienced by others. I thought Bob's post in this thread suggested that he does see it from time to time. Note also that others could see the problem yet be unable to notify anyone via the forum.

Regardless, you are probably correct that this is an AT&T problem. Things did work a few months back. It's still surprising that the problem is sensitive to my IP address. I wonder if different hardware could be in use when I get the IP address that works.

It's also surprising that I can access many forums and secure websites without problem. However, it's possible CNET uses some protocol not commonly used by others.

Calling this problem into AT&T is a good suggestion but as you mentioned would probably be difficult. I'll consider that at a later date. I think I will just live with the situation for the time being and hope it resolves itself. It's possible that something will change in the normal course of repairs, reboots, and software updates.

Thanks again for all the help.

- Collapse -
Test with New Computer
Mar 12, 2014 2:34PM PDT

Test 1 2 3

Test 4 5 6

Test 7 8 9