Results 1 to 6 of 6

Thread: Winsock Winsock Winsock

  1. #1

    Thread Starter
    Hyperactive Member razzaj's Avatar
    Join Date
    Oct 1999
    Location
    jounieh
    Posts
    261

    Angry

    ok there : It is not the first time I use winsock .. nor the second time ... it is maybe the 100'th time but I am facing some weird phenomena ....

    I know the Code to initiate connection (TCP) between 2 PCs is correct the way I worte it (come on .. )
    but it just wouldnt work ,the Connection Request doesnt eve get to the Second PC !!! when I run the program on diffrent pcs ..

    it only works when I run it on the same pc (I run it twice ) ... I admit I dont understand .. the network is working fine , there are no problems related to that .. but winsockJust wouldnt connect !!! Pleaaase I am desperate for Help on this one ....
    - regards -
    - razzaj -

  2. #2
    Hyperactive Member
    Join Date
    Aug 2000
    Posts
    258
    Post some code . The connection request event only fires on the listening sock .



    []P
    Visual Basic 6 SP4 on win98se

    QUIT THE RAT RACE BECAUSE YOUR MESSING THE WORLD UP !!!!!

  3. #3

    Thread Starter
    Hyperactive Member razzaj's Avatar
    Join Date
    Oct 1999
    Location
    jounieh
    Posts
    261
    It is not the first time i do this .. I know how t works .. and believe me I know my code is correct .. otherwise why would it work , wen I run the Clients and server on 1 Pc ??
    it doesnt work when I try to run the Client on a pc and the server on a different one ... it is really weird ...

    The Code is huge i dont hink it would be of any help ...
    but I was just wondering if anyone have had the same experience before ???
    - regards -
    - razzaj -

  4. #4
    Hyperactive Member
    Join Date
    Aug 2000
    Posts
    258
    I haven't . Try the service packs maybe .
    []P
    Visual Basic 6 SP4 on win98se

    QUIT THE RAT RACE BECAUSE YOUR MESSING THE WORLD UP !!!!!

  5. #5
    New Member
    Join Date
    Dec 2000
    Posts
    1
    Connections on a single PC happen immediately after the connect method, while they can take several seconds when connecting to a second PC. A common mistake I've seen is to try sending data or testing the connection before it has had a chance to complete. For example:

    Winsock1.Connect "127.0.0.1", 1000
    Winsock1.SendData "some data"

    will often work because it is connecting to the local computer, but will fail when trying to connect to a different PC.
    -Bob

  6. #6

    Thread Starter
    Hyperactive Member razzaj's Avatar
    Join Date
    Oct 1999
    Location
    jounieh
    Posts
    261
    no I am not trying to send anything after the connect method ... I put a while loop testing for the ready state of winsock before sending anything ...

    and After I pressed the button Connect it took forever and still didnt reach the Server ... I think something is wrong ... Something is wrong ... definitely...
    - regards -
    - razzaj -

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width