Careful! That article relates to Windows 3.1 running on MS-DOS 6! Research into the error specifically to Windows 7/8.x/10 seems to point to firewall settings/issues, or DNS resolution.
1. Check your firewall settings and determine which network type windows thinks it's connected to (Domain, Private, or Public). This could be the first clue that the computer isn't detecting the network properly. Proper DNS and firewall settings are crucial for this. (often, add-on firewall products can affect this - the Windows firewall usually won't unless someone has modified the default settings incorrectly.)
2. Temporarily turn off firewall protection and try logging on again. (Don't stop the service! In fact, if the service is off/disabled, this could be the root of your problem.)
3. Verify that the DHCP service is running, which provides DNS helper services.
4. Check the DNS settings on the local computer. Are the DNS servers pointing ONLY to internal servers? A common mistake is to add an external DNS to the list, which will wreak havoc with AD operations, particularly if a system gets a response from the external DNS faster than the internal - it will become the preferred server and then nothing will resolve on your internal network.
5. Get a copy of NetDom (Server 2000 AND 2003 resource kits - 2 versions with different capabilities). Run the Query against the domain and see what it says.
Also, when "running as administrator", just be sure you recognize that they are different contexts and could return different results. Not likely for "net view" but definitely for things like "net use". Just a reminder that when you're deep in the weeds you don't let this stuff mislead your troubleshooting efforts. 
Glenn
_________________________
Actually I
am a Rocket Scientist!
