Getting connected

Started by Ann, Sep 01, 2007, 22:08:02

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Ann

Just signed up with IDNet and am finding that it takes half an hour to connect.  Constant error 718s.. remote computer didn't respond in a timely manner problem.  What's that all about?  It's like being back in the olden days when I was with screaming.net and it took an hour to connect every time.  I have to admit that I'm totally gutted.  This is not something that I've had happen with ADSL before.  Is it a common problem here?

Den

Hi Ann,
A great big welcome to idnet. As its Saturday evening all the young people are out and the older ones like me are in bed. I am sure Rik will be along soon and all will be resolved because he is a god and has connections. 8)
I came to idnet in June and its the best move I could have made and I am sure this will become true for you as idnet cares.     :banana2:
Mr Music Man.

Simon

Hi Ann,

As Den said, Rik will work wonders for you, but in the meantime, have you raised the issue with IDNet support?  They do often respond 'out of hours', so hopefully this will be sorted very soon.  In the meantime, have a Welcome Karma point to cheer you up!  :)
Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.

Rik

Hi Ann

What are you using to connect with, is it a Speedtouch 330 modem by any chance? If so, what OS are you using and do you have the latest drivers?

Most of us use routers, so connections are pretty much permanent. When I do lose sync, a re-connection takes just a few seconds.
Rik
--------------------

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

MoHux

#4
Quote from: tortoise......... Is it a common problem here?

Hello Ann, welome to the forum.  The answer is, 'NO it's not'.
As far as I can remember you are unique.

You don't say what you are using to connect.
If it's a router, try re-booting it (the router not the PC).  It could be it's got a DNS problem.
If that doesn't cure it, I am sure the others are right, and someone more knowledgeable will pick it up in the morning.

Mo

;)

Edit; Sorry Rik, I thought I heard you snoring!!  ;D
"It's better to say nothing and be thought an idiot - than to open your mouth and remove all doubt."

Ann

Hi guys,  yes a speedtouch with XP Pro but it's always worked before.  The last ISP blamed me when they kicked me off every evening but funny that doesn't happen any more. 

I do have a router but something is broken as the computer and router don't see each other.  I have to sort that but it might be an expensive sort so I keep putting it off.  I know once I start, I'll end up doing a new build and I really can't afford it.

I'll try raising a ticket or whatever you call it here, when I've worked out how.

Lance

Quote from: tortoise on Sep 03, 2007, 21:45:39
I'll try raising a ticket or whatever you call it here, when I've worked out how.


An email to support@idnet.net should do the trick!
Lance
_____

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

Rik

Hi Ann

I looked up the 718 error, and found this:

This problem tends to occur due to failure of the modem synchronising with the local exchange

* Recheck connection settings

* Restart your PC and attempt to reconnect as this can sometimes be caused by a synchronisation
   problem

* Recreate the Dial-up Connection

* If this problem has been ongoing for a long period an upgrade or repair of the modem drivers is
   required in case the modem drivers have corrupted.

and this:


718 - PPP timeout.

This error indicates a PPP conversation was started, but was terminated because the remote server did not respond within an appropriate time. This can be caused by poor line quality or a problem with the server (ISP). This error can occur when your modem has connected to the ISP and has sent username and password, but there is no response from the server. 

Sometimes, re-dialing will be successful.

This error can also occur if your ISP account has expired, or if the username or password you are using is invalid.

This error can occur if you have LCP extensions enabled in the TCP/IP Properties of the connectoid and your ISP does not support LCP extensions.

This error may also occur if you have one or more network cards in your machine, and the cards do not have TCP/IP protocol enabled, or if the TCP/IP settings are incorrect. (Go to Networking in Control Panel to examine the properties of your network adapters; or, if you are not using the network card(s), disable them in Control Panel->System->Hardware.)


I tend to feel that you should talk to support on this, so that they can watch your login attempt (and check the settings you are using).
Rik
--------------------

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

Lance

Ann,

Out of interest, what was your migration date?
Lance
_____

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

Ann

Migration date was 31st August.  Is that significant?

I'd suggest that if most of those settings were wrong then I'd never get a connection but I do, it just takes several tries.  I also have actually formatted and reinstalled the OS since migration, and it was bad before and is bad after.  And I never ever had this problem with Eclipse.  This is exactly the thing that made me think twice about IDNet.  Having a static IP surely means that if there's an error at t'other end it will always be there.  At least with the other way if you get a duff connection a quick redial sorts it.

Lance

A static IP is (as far as I know) unrelated to the authentication of the line.

Are you sure after your format you installed the latest drivers for your modem? Would it be possible for you to try a different modem/router to see if the problem is related to your current modem?

Have you contacted support yet about this?
Lance
_____

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

Ann

Two things.. firstly it seemed to have fixed itself or have been fixed as connection was first time for the last couple of days.. secondly I just fixed the router so woohoo.. no more worries anyway and a much faster speed.  Didn't realise how much the modem was holding it back.

Thanks guys, it concentrated my thoughts and spurred me on to sort the router.

Lance

Glad you have it sorted, Ann :)
Lance
_____

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