Is WINSOCK corrupted or not?

I am trying to troubleshoot a connectivity issue we are having with our terminal server and rdp connections overa vpn. In doing so I came accross this
http://support.microsoft.com/kb/811259

"How to determine and to recover from Winsock2 corruption in Windows Server 2003, in Windows XP, and in Windows Vista"

Even though the article says it is for windows server 2003, there are no instructions for windows server 2003 in the article."

So based on the XP instructions, if I run "Msinfo32" and check the Components/Network/Protocol/" I should have 10 sections in the list.

I only have four.

the KB says "If there are fewer than ten sections, there is information missing."

So I tried the MS fixit and rebooted. Checked again and I still only have 4 sections

Tried the "netsh winsock reset" rebooted and still only 4 Sections.

So is my winsock corrupted or not. If so how do I fix it?

This is what is listed:

Name      MSAFD Tcpip [TCP/IP]
Connectionless Service      No
Guarantees Delivery      Yes
Guarantees Sequencing      Yes
Maximum Address Size      16 bytes
Maximum Message Size      0 bytes
Message Oriented      No
Minimum Address Size      16 bytes
Pseudo Stream Oriented      No
Supports Broadcasting      No
Supports Connect Data      No
Supports Disconnect Data      No
Supports Encryption      No
Supports Expedited Data      Yes
Supports Graceful Closing      Yes
Supports Guaranteed Bandwidth      No
Supports Multicasting      No
      
Name      MSAFD Tcpip [UDP/IP]
Connectionless Service      Yes
Guarantees Delivery      No
Guarantees Sequencing      No
Maximum Address Size      16 bytes
Maximum Message Size      63.93 KB (65,467 bytes)
Message Oriented      Yes
Minimum Address Size      16 bytes
Pseudo Stream Oriented      No
Supports Broadcasting      Yes
Supports Connect Data      No
Supports Disconnect Data      No
Supports Encryption      No
Supports Expedited Data      No
Supports Graceful Closing      No
Supports Guaranteed Bandwidth      No
Supports Multicasting      Yes
      
Name      RSVP UDP Service Provider
Connectionless Service      Yes
Guarantees Delivery      No
Guarantees Sequencing      No
Maximum Address Size      16 bytes
Maximum Message Size      63.93 KB (65,467 bytes)
Message Oriented      Yes
Minimum Address Size      16 bytes
Pseudo Stream Oriented      No
Supports Broadcasting      Yes
Supports Connect Data      No
Supports Disconnect Data      No
Supports Encryption      Yes
Supports Expedited Data      No
Supports Graceful Closing      No
Supports Guaranteed Bandwidth      No
Supports Multicasting      Yes
      
Name      RSVP TCP Service Provider
Connectionless Service      No
Guarantees Delivery      Yes
Guarantees Sequencing      Yes
Maximum Address Size      16 bytes
Maximum Message Size      0 bytes
Message Oriented      No
Minimum Address Size      16 bytes
Pseudo Stream Oriented      No
Supports Broadcasting      No
Supports Connect Data      No
Supports Disconnect Data      No
Supports Encryption      Yes
Supports Expedited Data      Yes
Supports Graceful Closing      Yes
Supports Guaranteed Bandwidth      No
Supports Multicasting      No
DCJ-TXAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

TribusCommented:
Give these two articles a good read, without knowing the background of your issue it is hard to determine what actually happened, but read through these and see what you get:

http://compnetworking.about.com/od/windowsnetworking/qt/winsockfix.htm

http://compnetworking.about.com/gi/o.htm?zi=1/XJ&zTi=1&sdn=compnetworking&cdn=compute&tm=29&f=10&tt=13&bt=1&bts=1&zu=http%3A//support.microsoft.com/kb/811259
0
DCJ-TXAuthor Commented:
Thanks But those don't help they both just link back to the same MS KB article I mentioned in my post. With no instructions for windows server 2003
0
TribusCommented:
0
Cloud Class® Course: SQL Server Core 2016

This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.

DCJ-TXAuthor Commented:
yeah, I tried that too but Still have the same results.

Thanks
0
TribusCommented:
Guess I will let a better Expert take a shot then.  You may end up making a a backup and have to re-install your server....
0
Khandakar Ashfaqur RahmanExpert/ConsultantCommented:
Do you see any Socket error into Event log ?Here is the error code of Windows socket error:
http://msdn.microsoft.com/en-us/library/windows/desktop/ms740668%28v=vs.85%29.aspx

For Windows 2003 check the following link to fix Winsock error:
http://support.microsoft.com/kb/325356

To check winsock catalog: netsh winsock show catalog
And check the following link that shows how to use netdiag to determine winsock corruption:
http://www.computerperformance.co.uk/w2k3/utilities/windows_netdiag.htm
0
DCJ-TXAuthor Commented:
No, I am not seeing socket errors in the events.

Thanks, looks like netdiag might help but I dont have suppot tools installed. I'll have to hunt down my cd.
0
ChiefITCommented:
There is a problem with supporting SP2 and Terminal Services. The problem with service pack two is it tries to set the listening port of the server to something other than the default 3389 error.

Your Winsock is probably not broken, your TS is probably listening on the wrong port.

The Winsock is a mixture of the IP address and application port. If you can ping the machine and telnet to the port, it's not a winsock problem.

Using Administrator priveleges,  To see what port your Terminal Services is listening on, go to the server's command prompt and type: Netstat -ab

Is terminal services listening on port 3389? If not, you have a problem.

Also read about terminal services listening on the wrong port:
http://www.lan-2-wan.com/2003-SP2.htm
0
DCJ-TXAuthor Commented:
I am not sure which fixed it but I followed this artical a second time. And I made a static arp entry for the terminal server in my firewall. One of the two resolved the problem.

Though I still don't understand why the ms artical says I should have 10 entries but I only have 4.

Thanks for all the help.

http://support.microsoft.com/kb/317518
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
TribusCommented:
Glad I could help it's why we do what we do here at EE!
0
DCJ-TXAuthor Commented:
I had already tried this before it was suggested. But tried it again afterword. Also I created the static entry and really don't know which fixed it.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Internet Protocols

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.