ethernet ports?!?!.. this will take a pr0!

[Floodie]

"Right!".... and that is said with distinct venom in my voice... My new pc almost had the pink fist of death!

I'm ALMOST there with my new build... installed everything, ported all old stuff over.. Before i start, i THINK my problem is due to a dodgy xp install (nemesis) and its screwed up my TCPIP..... Anyway, your all free to try and help!! plzzzz...

Ok, the problem is this : When i connected my virgin cable modem via wire to ethernet port on mobo it doesnt work....

Things i have tried :
- I have connected it via wire from modem direct to ethernet on back on mobo and all that happens is on my screen it says something like "Limited or no connectivity" with a yellow hazard triangle... when i unplug the wire from the mobo it goes away so i know the port KNOWS something is plugged in
- i have reinstalled all mobo drivers for ethernet ports
- i have in network connections "disabled" > rebooted modem > then "enabled" the connection and still nothing....
- A virgin engineer(yes they call then "engineers" now) was round earlier today to sort out my slow broadband connection.. i gave him a handjob if he would take a lot(jk! of course! men dont do that to other men!)... he came away stumped and couldnt fix it...
- i bought a separate ethernet card.. plugged it in, installed all the sware for it... rebooted modem.. plugged in the ethernet wire and exactly the same problem... "limited or no conectivity"... jesus....
- Rang virgin tech, on phone for 20 mins.. YES phone a mobile(gulp).. he concluded after various things (which i had just done anyway!) that i had to write "TCPIP" down and speak to a "pc support" place so they can fix it... i acted dumb as he was being a patronising c*nt and asked if my drivers for my mobo are all fine.. he said my drivers are fine but its my "TCPIP" files are wrong...

Anyway, I mentioned near the top about my friends dodgy xp install disc he gave me.. its called something like "Xp Nemesis" which comes with a load of software as its some kind of "beta" thingie... god knows...

there you go you pr0's!... what do you think!?!??...

 

[JoelDee]

Dunno without having a look at it really

 

[KDF]

The cable modem bonds with the MAC address of your computer.

ipconfig /release

to release any IP's your comp may have picked up. Power down the computer, power down the modem.

Leave it off for 5 minutes, power the cable modem wait till its negiotiated/handshaked with VM and power the computer. You should now get a full connection.

 

[Chrisjk]

What chipset drivers is your mobo using? If its nVidia make sure the built in firewall is turned off.

 

[Floodie]

KDF : i THINK i have tried that but will give it a go in a bit thanks..

Chrisjk : its nVidia yes... ive seen no sign of a built in firewall,..i will take a look - off top of head, do you know roughly where it is?.. actually chris, i see your point there but how does that explain why my ethernet card that i bought doesnt work either?... no nvidia stuff on that

Also, just to add..... when i plug the ethernet wire into my "old" pc.. i.e: the one im using now!.. it works fine!.. so its not the modem or router...

I am going to try and sort this shortly.. Ive been at it all day and i have just reset this all back up upstairs again... need to lug it all downstairs to test bits out.. will get back to you when ive tried it.. many thanks

 

[Chrisjk]

When i initially set up my pc and tryed to connet to my network i had no end of issues as nVidias firewall was interfearing with microsofts. It will be either a little icon in the right hand bottom corner or listed in start bar under nforce something or other.
I remember now, i couldnt get any incoming packets becuase nforce had blocked the port, however i was able to transmit out.

 

[Chrisjk]

The exact name of the firewall program is nVidia Active Armour

 

[Floodie]

Cheers chap will take a look... active armour doesnt rung much of a bell...

 

[Floodie]

right - fixed it... there is actually a SP2 fix available but i didnt need to use it..

i repaired the TCP/IP stack
"netsh int ip reset resetlog.txt"
then the Winsock
"netsh winsock reset catalog"

rebooted and woo... unsure if i should apply the fix from microsoft too as its fixed now.. "if it aint broke..." and all

Although im suspicious of my dload speeds... dropping very low for a 20mg connection.. but hey, its a sat afternoon, high useage i guess...

thanks for people help yet again