NIC settings changed to allow connection
 

After using the same PC hardware combo for the last couple of years, my ntl
BB decided that it was going to stop working today. A quick call to the
helpline had me going through all the usual IP release/refresh stuff but to
no avail. I even swapped (new) NIC's and PCI slots and a different PC to connect via the STB (Samsung) with no luck. I called again and (to cut a long story short) it connected again after changing the settings in the 'network connections' --> 'Configue' --> 'Advanced' tabs from auto setting (working for years with no problems) to '10BaseT Half Duplex' from the list of options. They couldn't or wouldn't explain why this was and seemed quite evasive when I pressed the point that things were OK one day, then not the next when there was no change my end. Does anyone know why if ntl are changing the techie goal posts and should I be concerned, or is this a MS/XP thing?

Cheers.

Re: NIC settings changed to allow connection
 

:welcome: to Cableforum!

It could be an MS/XP thing (XP does occasionally have trouble with autonegotiation, particularly if the card is based on an Intel chip), but it could also be a faulty ethernet cable.

Re: NIC settings changed to allow connection
 

This is a standard fix for ethernet auto-negotiation problems. "10Base T Half Duplex" is the safest option, that should work in most circumstances when auto-negotiation fails. When an ethernet link starts to go dodgy, it is usually auto-negotiation that fails first. Long ethernet cables are tricky for auto-negotiation: try a shorter one and see if that works. If a shorter cable solves the issue, look at the original long cable for any signs of damage.

"!0Base T Half Duplex" still provides more than enough throughput for your cable connection.

Re: NIC settings changed to allow connection
 

Quick question if you dont mind following on from that...?!?

will this cause any problems with the eventual switch to 10meg connections, & if its set at half duplex will this interfere with things such as p2p running at top end speed, as from my understanding of duplex settings, its in realation to being able to send / rec packets either together or only one at a time....

TIA
Barfly

Re: NIC settings changed to allow connection
 

Yes need 100Mbit full or half duplex.

Not an issue the extra latency introduced from half duplex operations is in the microseconds :)

You're welcome.

Try running it on 100base full duplex, if it can't do this points to a potential issue with the kit. Try it on 10base full duplex see if that works too. 100 base uses more pins on the cable than 10 so may want to see how it goes changing the cable if that doesn't work.

Otherwise an auto-negotiation issue, nothing too major just set 100base full on the card and enjoy :)

Re: NIC settings changed to allow connection
 

This seems to be an issue with Samsung STB's. I have a friend who was swapped from Pace to Samsung recently, and he could not get his Samsung to link with his 3COM 3C905 (ie a good quality) network card unless he forced it to use 10mbit half duplex. This is odd, as the Sammy has an Intel NIC in it, and the old Pace had a very naff Crystal one :)

Re: NIC settings changed to allow connection
 

I had this problem with the said cure and use p2p. The highest download i get now is about 30k. Considering i'm on a 2mb connection i'd expect it to be more like 200k or thereabouts. Doesn't matter how many seeds either. very annoying.

Re: NIC settings changed to allow connection
 

That is not a side effect of the 10mbps half duplex fix. There is still more than sufficient bandwidth in 10mbps half duplex to run a 2mbit connection.

Re: NIC settings changed to allow connection
 

if you have one end of a connection set to 10fd and connect at 10hd you will get collisions and it even affects a 2mbit connection.

Re: NIC settings changed to allow connection
 

Collisions would not slow the speed to sub 2mbit.

You may want to try forcing 100mbit mode, according to a freind who knows quite alot about network gear, sometimes it is just autonegotiation that goes wrong and if you force both to 100mbit, it works great. Try it, it can only not work :)

Re: NIC settings changed to allow connection
 

I have had a incorrectly negotiated ethernet - modem connection reduce upload to under 50% speed and down made erratic between 40% and 100% speed, this is on 2mbit with a ambit120 modem. It can be repeated time and time again if I deliberatly use bad negotiation.

Likewise on a basic lan setup if you use poor negotiation, collisions arent a thing that only affect it on high utilisation it will just run poor full stop, latency jumps every few seconds and poor upload speeds.

Your advice is right to force both to the same setting, that I agree with.

Re: NIC settings changed to allow connection
 

I'm away at my girlfriends til Thursday so I'll give it a go then. What i don't get is that it ran fine for a few months after the Samsung stb was put in, then it went funny on me. That half duplex fix works but doesn't seem to do well with the p2p stuff. I'll let you know what happens.

Re: NIC settings changed to allow connection
 

changed it to 100 meg on full and half, no joy. did the 10 meg on full and am trying that but the p2p is still rubbish.

Re: NIC settings changed to allow connection
 

the 10 meg on full and half work fine but the 100 meg on full and half seem to have issues. does this actually mean anything?

Re: NIC settings changed to allow connection
 

well when you changing nic remember the modem has a setting for the modem side of it as well, so if your modem is set to 10mbit then setting your nic to 100mbit is bad. It is best to leave your nic on auto whilst setting the modem so you can connect again right away then after set the nic to what the modem is set to.