Did you turn off networking? Delete the NIC in the hardware manager? This goes WAY back to the Win95 clients in an NT4 domain, but adding the NIC back in (then re-installing the networking components) worked every time. -- Richard D. McClary Systems Administrator, Information Technology Group ASPCA® 1717 S. Philo Rd, Ste 36 Urbana, IL 61802 [email protected] P: 217-337-9761 C: 217-417-1182 F: 217-337-9761 www.aspca.org The information contained in this e-mail, and any attachments hereto, is from The American Society for the Prevention of Cruelty to Animals® (ASPCA ®) and is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution, copying or use of the contents of this e-mail, and any attachments hereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify me by reply email and permanently delete the original and any copy of this e-mail and any printout thereof.
<[email protected]> wrote on 10/05/2010 03:34:18 PM: > Yes. I went through and turned off any services not absolutely > necessary. Checked processes, too. > > > From: [email protected] > > To: [email protected] > > Subject: RE: socket error when trying to join domain > > Date: Tue, 5 Oct 2010 14:46:03 -0400 > > > > Have you checked the Windows Firewall settings? Try disabling the firewall > > and re-try joining the domain??? > > > > > > > > From: [email protected] [mailto:[email protected]] > > Sent: Tuesday, October 05, 2010 2:24 PM > > To: NT System Admin Issues > > Subject: socket error when trying to join domain > > > > XP sp3 computer. It's brand new, just got it in. When I attempt to join > > the domain, I get the following error: > > > > "An operation was attempted on something that is not a socket." > > (error code 0x00002736 WSAENOTSOCK) > > > > Googling the error, the only thing I could find was an MS kb to replace > > Winsock and Winsock2. I got those keys from another XP pc and merged them > > in. Unfortunately, that did not fix the problem. > > > > Since I had joined a server to the network that same day, I don't believe > > this is an issue where it can't contact a DC. I've put >500 pc's on our > > network and never had this error before. > > > > I'm starting to think a wipe and reinstall may be the only solution. > > Thoughts? > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > > > --- > > To manage subscriptions click here: > > http://lyris.sunbelt-software.com/read/my_forums/ > > or send an email to [email protected] > > with the body: unsubscribe ntsysadmin > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > > > --- > > To manage subscriptions click here: http://lyris.sunbelt-software. > com/read/my_forums/ > > or send an email to [email protected] > > with the body: unsubscribe ntsysadmin > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > --- > To manage subscriptions click here: http://lyris.sunbelt-software. > com/read/my_forums/ > or send an email to [email protected] > with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
