DHCP Enabled, Automatic IPs, Manual DNS and whatnot.
But one ocmputer, with identical settings, and guaranteed working drivers refuses to work unless I give it a manual IP. And even ten it doesn't get internet access. Any ideas what coudl be causing it?
Name:
Anonymous2005-08-08 0:12
By the way, this all happened only after I ran a WPA killer on the computer. Would this have been the cause? How do I reverse the effects?
Name:
Anonymous2005-08-08 5:58
Provide more info.
Name:
Anonymous2005-08-08 11:38
Such as?
Name:
Anonymous2005-08-08 12:03
OS, general network setup, etcetera.
I have no trouble with this mess when I let my router assign addresses... but on 386 systems, I manually set the IP address on account of MS TCP/IP being so limited on them.
Name:
Anonymous2005-08-09 19:28
You've definitely got the right drivers? I had a weird issue with XP and a Tamarack network card the other day - XP thought it was an ASound brand card, it appeared to be working, but wouldn't ping correctly or anything. XP was preferring its own ASound drivers to the correct Tamarack drivers because the former were MS certified and the latter not. Had to go through the update drivers using manual selection at stages. I'm just curious as to how you know they're "guaranteed working drivers" - in my experience there's no such thing as "guaranteed"! Just a thought.
Name:
Anonymous2005-08-14 2:36
It was a winSOCK error. I just ran a winsock cleaner thinger.
Name:
Anonymous2005-08-14 5:07
Winsock cleaner thingie? Sounds like something I would never run on my computer.
Name:
Anonymous2005-08-14 6:05
Dirty socks, LOL.
Name:
Anonymous2005-08-14 6:26
I remember when winsock first came out for Windows 3.1. It was on the cover CD of all the magazines and I was like "wtf is this shit?"
Name:
Anonymous2005-08-14 8:06
Trumpet Winsock had a real shitty password encryption. As a kid I broke it, visited a bunch of libraries and copied the strings out of the INI files, and started surfing for pr0n using free internet at home.