Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 21

Thread: Strange Networking Issue

  1. #11
    AOs Resident Troll
    Join Date
    Nov 2003
    Posts
    3,152
    Try it with one card first...

    after the OS install (and updates) add the second card...I seem to remember this as an issue with 2 NICs... 2000 server.....during an install.


    or you have a cable\connectivity issue

    MLF
    How people treat you is their karma- how you react is yours-Wayne Dyer

  2. #12
    Senior Member
    Join Date
    Jul 2004
    Posts
    469
    When you say, "reinstalled OS", did you do a fresh install, or just rerun setup?

    Initially I was going to say, make sure the DHCP service was running on the client, but after the rest of the ts you've done I doubt its that. Still worth a look though.

  3. #13
    Actually, Morgan, I've tried it with both cards alone (I suspected too that it could be a problem with both running simultaneously), and then with a third card by itself.

    zENGER, The setup was a Windows repair installation. I didn't want to wipe the drive with a fresh install.

    However, if you'll notice from my other thread, I'm getting "memory cannot be written" errors during the repair. I believe it's occuring when COM components are being installed. I've tried it with three different memory sticks, and it still persists.

  4. #14
    AOs Resident Troll
    Join Date
    Nov 2003
    Posts
    3,152
    Did you try HTRegz winsock fix

    I had a machine where this was the issue...and a repair did not work!!!

    Caused by malware and antispyware removal

    The networking was so fu$%ed up...it was unrepairable

    More Info

    http://compnetworking.about.com/od/w...winsockfix.htm

    http://www.google.ca/search?hl=en&q=Winsock+fix&meta=

    Try the fix or a format reinstall

    Probably fix your memory read errors too

    I think it may be all tied together

    MLF
    How people treat you is their karma- how you react is yours-Wayne Dyer

  5. #15
    THE Bastard Sys***** dinowuff's Avatar
    Join Date
    Jun 2003
    Location
    Third planet from the Sun
    Posts
    1,253
    If you're ready to fdisk and re install, try this first

    Go to Run > regedit > and delete the following

    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock2

    Restart the computer
    Go to Network Connections
    Right click and select Properties
    Click on the Install button
    Select Protocol
    Click on the Add button
    Click on the Have Disk button
    Go to the \Windows\inf directory
    Select anything there and click Open
    Highlight Internet Protocol (TCP/IP)
    Click on the OK button
    Check to see if your network adapter obtained a new IP lease and if not...
    Reboot
    09:F9:11:02:9D:74:E3:5B8:41:56:C5:63:56:88:C0

  6. #16
    WinsockFix didn't fix the problem unfortunatley.

    \Windows\inf
    Where is this located? Either I'm blind (likely) or I don't have a folder by this name in plain view...

  7. #17
    Senior Member nihil's Avatar
    Join Date
    Jul 2003
    Location
    United Kingdom: Bridlington
    Posts
    17,188
    Not sure why, but is your LSP stack OK?

    http://www.cexx.org/lspfix.htm

    I have certainly encountered it as a problem with internet connections.


  8. #18
    THE Bastard Sys***** dinowuff's Avatar
    Join Date
    Jun 2003
    Location
    Third planet from the Sun
    Posts
    1,253
    Originally posted here by AngelicKnight
    WinsockFix didn't fix the problem unfortunatley.



    Where is this located? Either I'm blind (likely) or I don't have a folder by this name in plain view...
    It's a system folder, you need to select show system files and folders under the tools - folder options- view tab - In explorer
    09:F9:11:02:9D:74:E3:5B8:41:56:C5:63:56:88:C0

  9. #19
    Hey Nihil,

    The LSPFix program didn't discover any problems.


    Dinowuff,

    Tried your trick as recommended, but no luck.


    Now is this just wierd as heck or what? I'm about to move the HDD over to another box and see what happens booting up from that one.

  10. #20
    AOs Resident Troll
    Join Date
    Nov 2003
    Posts
    3,152
    You know I was on a machine last night...receiving read memory errors....

    And I noticed the machine was running extremely low disk space on the system partition...

    >by the way>User is a computer *spurt*...machine has 3 partitions...with everything possible residing on C:\

    Could be the part of the problem??? lack of disk space

    You know how windows loves memory...needs memory...and really starts to actup when it cant get any....it appears you have many issues on this box

    As for moving to another box...you are slaving in the hard drive...cause if the board and other hardware are not the same...it wont boot! as a boot drive.


    Slave it in..remove the data...and format reinstall from scratch....should solve your issues...


    MLF
    How people treat you is their karma- how you react is yours-Wayne Dyer

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •