Winsock.RemoteHost = "www.netscape.com"
    Winsock.RemotePort = 80
    Winsock.Connect

    Winsock.SendData "GET / HTTP/1.0" & vbCrLf & "Connection:
Keep-Alive" & vbCrLf & _
                        "User-Agent: bs" & vbCrLf & _
                        "Accept: image/gif, image/x-xbitmap, image/jpeg,
image/pjpeg, image/png, */*" & vbCrLf

i always get the error  40006. wrong protocol or connection state
how should i do it?

/konrad

Private Sub Command1_Click()
Text1 = ""
Winsock1.Protocol = sckTCPProtocol
Winsock1.Connect "www.microsoft.com", 80
End Sub

Private Sub Winsock1_Connect()
Dim sText As String

    sText = "GET /default.asp HTTP/1.0" & vbCrLf & "Accept: text/html" &
vbCrLf & vbCrLf
    Winsock1.SendData sText
End Sub

Private Sub Winsock1_DataArrival(ByVal bytesTotal As Long)
Dim sText As String

    On Error Resume Next
    Winsock1.GetData sText
    Text1 = Text1 & sText
End Sub

Private Sub Winsock1_Error(ByVal Number As Integer, Description As String,
ByVal Scode As Long, ByVal Source As String, ByVal HelpFile As String, ByVal
HelpContext As Long, CancelDisplay As Boolean)
    MsgBox Number & " - " & Description, vbCritical, App.Title
End Sub

Try using the Winsock API itself and not the Winsock control.  The
Winsock control takes more resources and is less flexible.  Also, the
winsock control is much slower than using the API's.

Another thing to think about is that the http protocol supports both UDP
and TCP streams on port 80 -- this can be found in the RFC's.  

So, If you want performance, flexibility, and reliability -- don't use
wrapped up code when you have access the API's themselves.  If you would
like, I can send you all the code you'll ever need to do winsock
programming.