Lost connection over the weekend, anyone else?

Started by goldmercury, Apr 16, 2007, 12:03:27

Previous topic - Next topic

0 Members and 2 Guests are viewing this topic.

goldmercury

Syncing but can't ping to anywhere.  DSL disconnected.  Anyone else having issues?  2nd weeek with ID Net  :-\

cavillas

No. Alright here.  Contact Support if you are concerned, they can help.
------
Alf :)

Rik

Quote from: goldmercury on Apr 16, 2007, 12:03:27
Syncing but can't ping to anywhere.

Hi and welcome to the forum. Have you been posting about this problem over on ThinkBroadband? (I just don't want to repeat all the advice you've been given there...)
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

goldmercury

have not posted at think bb.  I'm a system admin so have done all the checks at my side and can confirm it looks like a problem at the ISP.  Don't think it's the exchange as I'm syncing fine just can't connect.

What info has been posted on think broadband forums?  I

Rik

The TB thread is here.

Have you contacted support at all? That might be the quickest route, as they will be able to 'see' your line.

I take it you can ping your router, but not the web? Are you picking up DNS automatically or do you have the servers set in manually? It might be worth trying an alternate DNS server pair, eg  213.208.106.212 and 213.208.106.213. That would eliminate the IDNet DNS from the equation, though they are working fine for me.

What MTU/RWIN are you using, have you checked your hosts file?

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

psp83

Quote from: rikbean on Apr 16, 2007, 12:39:17
What MTU/RWIN are you using, have you checked your hosts file?

Saves me posting a new thread asking, what is the recommended mtu for idnet. at the moment mine is set to 1500, idnet say it doesnt matter if its set between 1458 - 1500.

Rik

It depends who you talk to. :) Miriam recommends 1458, and for me that has worked best, I use an RWIN of 65228. However... Every line has different characteristics, and will, therefore, benefit from a larger or smaller RWIN in particular. I always recommend leaving the router 'wide open' at 1500 and making all the changes from within Windows.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Rik

Quote from: goldmercury on Apr 16, 2007, 12:03:27
Syncing but can't ping to anywhere.  DSL disconnected.  Anyone else having issues?  2nd weeek with ID Net  :-\

Just another thought, it might be you have a stale session. Try unplugging the router for 30 minutes.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

psp83

Quote from: rikbean on Apr 16, 2007, 12:55:03
It depends who you talk to. :) Miriam recommends 1458, and for me that has worked best, I use an RWIN of 65228. However... Every line has different characteristics, and will, therefore, benefit from a larger or smaller RWIN in particular. I always recommend leaving the router 'wide open' at 1500 and making all the changes from within Windows.


Have you got a link to a program i can use to change the settings in windows? i had one but cant remember what is was called.

Rik

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

MoHux

Rik, I see you use an RWin of 65228.  I can't help thinking that for dial-up this would be o.k. but for Max it's too low.
Granted, it is a multiple of your MSS (1418x46), but for Max I feel you could scale it up by multiplying this by 2.

i.e. 65228x2=130456.

This leaves your MTU untouched at 1458.

If you do this don't forget to switch Windows Scaling 'ON' (anything over 65535).

Might be worth a try ........  ;)
"It's better to say nothing and be thought an idiot - than to open your mouth and remove all doubt."

Rik

Hi Mo

Thanks for the tip. I did try the larger figure when I was tweaking, but I found that packet loss started to occur above about 65K. Maybe it's time to try again, see if my line characteristics have changed?
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

goldmercury

rikbean ,

have talked to support, what a difference compared to Demon, quick personal response.  They could see me synced but not logged in, got me to confirm username password which were correct.  It looks like a stale session which has been reported at think BB. 

DNS servers were assinged. MTU is 1460.

BT speedtest worked when logged in under the test account.  I turned the router off for an hour and back on, everything is now working fine however I'd like to know why this happened as my office was down for a day and don't want it to happen again.


Rik

Quote from: goldmercury on Apr 17, 2007, 10:15:56
have talked to support, what a difference compared to Demon, quick personal response.

You'll get used to it after a while, it's why we all go around with smiles on our faces - not a script in sight! :)

QuoteThey could see me synced but not logged in, got me to confirm username password which were correct.  It looks like a stale session which has been reported at think BB. 

I did have that thought after re-reading your post.

QuoteBT speedtest worked when logged in under the test account.  I turned the router off for an hour and back on, everything is now working fine however I'd like to know why this happened as my office was down for a day and don't want it to happen again.

No-one has ever been able to explain to me the cause of stale sessions, essentially they come down to BT's equipment thinking you have a live PPP session, whilst in practice you don't - hence you sync but can't get to the web. The only cures I know of are the 'router off' trick, usually 30 minutes will do it, or logging in to the BT test account. Sometimes, that seems to wake up the exchange equipment. Unfortunately, it seems to be a BT issue, to the best of my knowledge, ISPs don't have a way to directly kick the connection back to life.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.