Nosebleed Moments

I’m not really a techie but something confuses me about the TCP world.

Resetting TCP (assuming you did the flushing of the DNS) using netsh int ip reset ip on a NO BROWSE issue, and then you do WINSOCK reset, netsh winsock reset all, it could actually resolve the issue.

however, I think

TCP is a big umbrella, and under it are the components such as the DNS Settings. Resetting the whole package of TCP would also result in flushing of the DNS right? If I am correct, no need for you to do the ipconfig /flushdns because it’s basically redundant to do that. Also, WINSOCK is (I think) under the TCP umbrella as well, according to a friend when solving a NO BROWSE issue, these are twins, you have to do the reset TCP and after that WINSOCK, so what’s the use of WINSOCK reset if you already reset the TCP which in fact only after executing that command will result in rebooting the computer, and if you do TCP resetting, it will not prompt you to restart the computer but you can do a manual reset of the computer right?

But I researched on it and says that 

Winsock (short for Windows sockets) is a technical specification that defines a standard interface between a Windows TCP/IP client application (such as an e-mail client or an FTP client) and the underlying TCP/IP protocol stack. (for full article… click here)

So If that is the case? when will be the best time to reset the WINSOCK?

So Anu ba talaga kuya!?

I am so confused right now, I need enlightenment.

~ by jcmontales on April 7, 2008.