Bd.net blocked, help please!

Yeah. Off and on. I know they are working on it. Good luck, Jeff and all diligent helpers. Thanks.

 

Well, after a day of frustration trying to stabilize the Brocade MLXe-16 routers, the datacenter's network engineers rolled back to the proven cisco 6500 gear.

Sorry again for all the issues today.

 

It's all good, Jeff. You have to try new things to see what works. We are boatbuilders after all and know the risks of experimenting with innovation.

 

No worries we know how hard you guys work to keep this place running, its just an addiction. Too much time away from Bd.net and we start exhibiting withdrawal symptoms

 

That is exactly right. I was Jonesing to read up to the point I was getting the shakes and my eyeballs were starting to roll back in my head.

 

Same problem here.

I can login and open a few threads or reply a PM, then I get a timeout error opening the next one.

It happened, as I said, already many weeks ago and is not related with server updates.

I used "internet exploder" to try if FOX might be the problem, no access, timeout error.
Tried several DNS servers to no avail, it must be on this side (bd.net) of the wire.

Any ideas Jeff?

Richard
(at the moment: 88.242.2.67 but that will be different tomorrow)

 

To confirm, does the same blockage happen if you are browsing with either Internet Explorer or Firefox as a browser (or Chrome or Safari)?

Are you running any unusual security software?

When you encounter the problem (before and at the moment you are blocked) are you going through any type of tunnel/proxy that you know of?

I'm looking for anything non-standard that may be causing truncated or malformed requests to the webserver which in turn trigger the firewall to think it is being scanned or probed vs. normal browsing activity. I'm still looking at the logs to see if I can figure out why you are being blocked intermittently.

 

Thanks for the effort Jeff.

No, I did not change anything and IE does not make it better than Firefox, my standard browser.

I do not use any proxy, DNS server or redirecting software, except now.

Using "Vtunnel" gives me acccess, and "Tor" a tunneling software does so too. I am using Tor in this moment, and have no problem.
But that can not be the solution.

My IP 88.242.2.67 when Tor is deactivated
or IP 92.241.190.188 when activated

But the former will change when the Marina resets the modem, for example.
The latter of course changes regularely.

Thanks again Richard

 

I've increased the logging level and made some adjustments which will hopefully solve this. Please let me know if you are blocked again. And sorry again for the inconvenience.

 

Thank you Jeff.

For typing this message I deactivated the tunnel, and it works now.

Lets see if it does on the next login. If not, I make a noise.

Richard

 

Hi Jeff,

it works to some extend now! I am logged in for a while now and can post and answer PM. But the system kicked me out twice again. It is no problem to login again and even the PM text is not lost. So we have already some success. Thanks to your efforts.

I checked if the IP changed between first login and first kick out, but that was not the case, I still have the same since three days now. I know this dynamic IP circus can cause such problems.

Can cookies be the problem?
My system accepts cookies from bd.net explicit, but refuses unknown sites.

Regards
Richard

 

It wouldn't hurt to clear any historical cookies from www.boatdesign.net boatdesign.net and forums.boatdesign.net and then login again to reset the current login cookie from www.boatdesign.net

A corrupt login cookie is rare, but it does happen. However usually a login cookie issue manifests itself with a persistent lack of ability to stay logged in on the next page or more often, a lack of ability to login at all.

 

Of course Jeff.

But my system clears ALL cookies when shut down.

Today I have not encountered any difficulties by so far.

 

Problem seems to be solved, thank you Jeff!

Maybe sensible to remove the thread. Who could benefit?

Regards
Richard

 

That's good to hear. I'll leave this thread for a little while just in case; I wish I could take full credit for the solution; however the last change I made in response to this was on 9/14 which seems to have solved the larger issue; I could not however find anything on our side that was causing the couple of lesser intermittent glitches you experienced on 9/15.