Losing connection to Router Problem

[Pistol]

Hi guys, i have another problem to share with ye i fear :s

My router last night remained connected for 9 hours without a problem. I then powercycled it this morning. It booted up fine and connected no problem.
5 mins later i loose connection to the router... ie all the lights are fine on it, power, lan, adls and ppp, all still lit. However my pc cant connect to it, even to its admin page. I have to powercycle it to get it back.. and then its ok, until it drops again...

Not sure if this is the cause but i notice it happening when i am browsing and open pages in Firefox, not always, but when it happens, i have often just tried to open a tab, most often from google. Could this be an issue? DNS or something? It has been happening on and off for about a week. Sometimes within minutes, sometimes hours.

I switched out, filter, network cable, phone line cable, have it in master socket etc.. nothing different to when it can remain connected overnight without problem..

I am using a wired connection to my lan port 1 (have 2 ports) I disabled my 2nd in case it somehow oddly gave an issue.

Given that the ppp lights do not go out, and i dont loose synch i cant see it being an IDnet problem or an exchange problem, could i be wrong?

Any ideas please? Cheers

[Rik]

I doubt it's an 'exchange side' problem (BT or IDNet), as you can connect and 'talk to' a router without plugging it into the phone.

The fact that re-booting the router cures the problem would prompt me to start there. Do you have a spare you could try, or one that you could borrow? Alternatively, it could be a cable or port problem, so another diagnostic would be to change the cable and then, if the problem persists, use a different port on the router, then the other port on the PC.

Check in Device Manager that nothing is being flagged on the network side, if the above tests haven't cured anything, consider trying to find updated drivers for the NIC.

If none of that helps, I'd delve into the TCP/IP setup, but my hunch is that it's not that.

[Pistol]

Cheers Rik. I have a spare of everything, i already tried a different router and cables and ports, both on the pc and routers. Still the same..

I do wonder if it is my drivers...

I was running Win Xp fine.. didnt have this problem.. I clean installed Vista 64bit about a week ago.. the problems happened after that.

Device manager does not indicate a problem. It says that the drivers are the most up to date. I disabled the "allow pc to power down router" option in case that was an issue.

However.. my mobo is a EVGA 680i and it came with nvidia nforce network controller software. Now.. i wasnt sure if this was causing me a problem, as the install gave more limited options in vista than it did xp. I downloaded their vista 64 bit version and installed it. I think i then uninstalled the software (for teaming and gaming qos), but the drivers remain.

I have left tcp/ip settings all auto atm. perhaps i should set details there? Willing to test/try anything cheers.

Many thanks!

[Rik]

Now you've mentioned the dreaded V word, I'm at a loss to help you more. It increasingly sounds like a driver issue to me, but as I don't use Vista, I can't offer much in the way of practical advice. In your position, my next move would probably be to stick in a NIC if you have a free slot and see if that helps. However, a Vista user will be along soon.

[Pistol]

*chuckles* cheers mate, appreciated,  even just to converse and share my woes    I dont have a spare NIC unfortunately.

just in case it helps anyone help me, here are some bits of info from my network controller properties


There are a bunch of options within the driver advanced setting, not sure what they are.

driver provider - NVIDIA
driver date 29/01/2008
driver version 67.7.6.0
location PCI bus 0, device 17, function 0
This device is working properly


Flow control - disabled (default)
interrupt moderation - enabled
ip checksum offload RX and TX enabled
jumbo packet - 1514 bytes
large send offload v1 - enabled
large send offload v2 - enabled
large send offload v3 - enabled
llow power state link speed - enabled
network address   -not present
priority and VLAN - priority enabled
receive side scaling - enabled
speed/duplex setttings - auto negotiation
TCP checksum offload ipv4 - RX and TX enabled
TCP checksum offload ipv6 - RX and TX enabled
UDP checksum offload ipv4 - RX and TX enabled
UDP checksum offload ipv6 - RX and TX enabled
VLAN id - 1
wakeonlan from poweroff - enabled


Many thanks!


ps: is it possible that errors in the router could cause it to drop?

since i last powercycled it about 30 mins ago...

RS Uncorrectable errors: 8
RS Correctable errors: 2082

[Simon]

My name is Simon, and I'm a Vista user. 

Purely a shot in the dark, as I'm not too technically adept, but are you using the manufacturers drivers or Vista's own?  I believe sometimes they can be different, and I also seem to recall something somewhere about a Vista update messing with network settings / drivers.  Sorry not to be more precise.    

[Pistol]

Heya Simon heh    Good call.. hmm.. good question too.. i think i may have used both... not sure which currently.. :s

Ok, here is a screenie of my router stats, just in case they are useful. I think i will also reinstall nvidias drivers, just in case i am using vistas, though it does say nvidia on them..

cheers again

[Rik]

ps: is it possible that errors in the router could cause it to drop?

since i last powercycled it about 30 mins ago...

RS Uncorrectable errors: 8
RS Correctable errors: 2082

Errors can cause a router to throw a tantrum, but not at that kind of level (iac, it's more a case, usually, that the noise which is causing the errors triggers a re-sync).

ISTR, but can't find right now, reading of other people with nVidia drivers experiencing problems with Vista64... Hopefully, someone will be along with a torch shortly.

[vitriol]

Normally Nvidia's drivers are bulletproof, maybe check over at Nvidia to see if they have any newer drivers.

[Pistol]

Yer right Rik, just been reading some posts re problems with my mobo network and vista too :s Oddly they are from last year..so ye would think they would be sorted now.

Vitriol, cheers, but i cant see any download from nvidia for network controller..
See, i have a mobo install disk that came with my mobo, with network elements to install from it. It wont work with vista 64 though.. So the only thing i could find to download was from evga (my mobo) but it only has network manager software and none of the other parts to the install that i had in xp.

http://www.evga.com/Support/Drivers/

So its listed as a mainboard chipset driver install. Ill try redownloading and installing it again and see.

[Rik]

I've got everything crossed for you.  It does make typing hard though.

[Pistol]

hmm, someone on evga forum posted this as a possible solution to a problem which sounds just like mine.. i wont pretend to say i understand exactly why it would be.. but ill try it now - mine was set to auto negotiate.

"Alot of these problems are caused by Auto negotiate.  Does your router have GigE?  That speed of a connection can ONLY be done when using an onboard NIC connection via Autonegotiate for Speed and Duplex.  This is why I do not use the onbaord NIC because I do have GigE but prefer to set the Speed and Duplex manually to 1000bT Full Duplex.

Try going to the properties of your connection then configure the Ethernet card. On the advanced tab scroll down to Speed and Duplex then set the value to 100bT Full Duplex.  See if the problem persists.  If that does not correct the issue, use Wireshark to capture all packets when doing a DHCP renew.  Try to get one when it is working and when it is not working for comparison. "

lol i also read... "I had the same problem, but it was driver related. The "new" drivers didn't work (the ones on the disc that came with the mobo) so I got the ones from the Nvidia website dated 2006.   "

Then someone else says DO NOT use evga drivers!  lol.... but as i said i cant see nvidias ones to use instead! ahahaaargh. ok, here we go..

woot ok i found nvidias ones!, reporting back after dl and install and reboot

[vitriol]

Click on Download Drivers

Product Type : Nforce
Product Series : Nforce 6 series
Product : Nforce 680i SLI
Download Type : Driver
Operating System : Vista 64
Language : English (US)

Click on search

The Nforce platform chipset driver includes the following components

    * Ethernet Driver (v67.74) WHQL
    * Network Management Tools (v67.74) "Sedona"
    * SMBus Driver (v4.62) WHQL
    * Installer (v5.73)
    * SataRAID Driver (v9.99.09) WHQL
    * SataIDE Driver (v9.99.09) WHQL
    * RAIDTOOL Application (v9.99.09) "Sedona"


Good luck.

edit just read that you've found them.

[Pistol]

YOU ARE GODS AMONG TECHY PEOPLE!

Thank ye guys Installing nvidias drivers and not evga's  (touch wood) looks much better...

I vote for idnetters.co.uk to run the UK. No problem is unsolvable fer them!

[Rik]

We do try, mate - well at least people tell me I've very trying. Toes crossed you've got your solution. 

[Pistol]

Sorry one last question :O   

Rik, ye mentioned about router errors before - is there a rough number of acceptable errors (per hour or something?) under which its of little concern? Or if there are more than that amount...

eg. after 2 hours 30mins of uptime i have 0 upstream errors but on downstream:



RS Correctable Errors:     15784     0
RS Uncorrectable Errors:    36    0
Bit Errors:     0     0

cheers again

ps this is also in consideration of asking for interleaving to be turned off... to improve my ping times for gaming.  I am aware if errors are too many then it will drop my speed... so trying to get an idea of the wisdom of this. If support turning it off is instant, then i guess i can just test it if they can also instantly turn it on again if need be? Cheers

edit: i rang support anyway and asked for it to be turned off. Takes 24 hours i was told. So we will see what happens. Only 24 hours to turn on again if it turns out worse fer me anyway. Cheers

[Rik]

You have about 100 errors per minute there, so personally I would leave interleaving on. My own, noisy, line seems to generate about 12 errors/minute.

If the BT software thinks it necessary, it will turn interleaving back on in a flash, so you'll know for sure quite quickly.

[Steve]

You have about 100 errors per minute there, so personally I would leave interleaving on. My own, noisy, line seems to generate about 12 errors/minute.

If the BT software thinks it necessary, it will turn interleaving back on in a flash, so you'll know for sure quite quickly.

I often wondered that Rik, as it went on automatically in the first place but has to be manually removed. So logically unlees there is a permanent "off" switch there is no point having it removed as the next burst of errors will turn it back on

[Rik]

As I understand it, Steve, there are three 'positions' for the switch. Auto is the norm, and will use interleaving only if it thinks it necessary. On is what you'd expect but Off is more a "we've turned it off manually, but if the system wants it back, it will turn it on again".

[Pistol]

Here are the pics of my BT socket.. maybe ye can make sense of them. I cant see wiring anywhere to remove :s Note there is a little BT old looking socket to the left of the larger one.. is that normal? Or i need to go into it?

with the faceplate removed




removed the 2nd part of the plate (is that the bit i shouldnt touch?)




the back of the main part had no wires attached..




cheers

[Rik]

You don't have any extensions, and thus no ring wire, connected to that faceplate. If you did, the 'signal pair' would be on terminals 2 & 5, the ring wire would be on 3. The connections on the back (the exchange pair) should read A/B if labelled.

[Pistol]

Ah yes yer right, no extensions... doh i should have thought of that heh; and yes, labelled A and B. Cheers. Ok, im a wee bit wiser and know ive done all i can now.

I still think its a network setup issue for me. Is is usual to have 2 gateway addresses? I thought i had a local one - 192.168.1.1 and my WAN one (my static ip addy)?

I just noticed there is another ip addy in the router default gateway....

[Rik]

What does ipconfig /all reveal?

[Pistol]

Ugh..just back from 30 more mins of hair tearing heh. I ended up resetting the router a couple of times and then could connect to it but vista wouldnt see the net.. Finally called IDnet and James was very knowledgeable and helpful. It came down to my router being a **** and i told him i would try resetting it one more time.. so James..if yer reading this.. Cheers and it works again now heh.  Cant believe they would hide those NAT settings though?

ps Rik, James explained the extra gateway addy and so now all seems ok...

[Rik]

That's good.