Winsock control

Someone try this

using the winsock control connect to port 23 of any unix system. use http://www.kurtsimons.com if you want.

just attempt to talk to the system.
send a fake user name pass work
If you don't get all ????? back send me your code!

thanks

On your unix machine, all I get is a Port Block Message

Use regular windows telnet just to make sure its not your connection.

Kurt,
I have start a prelim. When I use UDP, nothing come back, when I use TCP i get a wrong protocl Type.

My code

form_load
tcp.localport = 0 ' lets system set port
tcp.remotehost = "www.kurtsimmons.com"
tcp.remoteport = 23
end sub

command1_click
tcp.connect
end sub

tcp_dataarrival
dim temp as string
tcp.getdata temp
end sub

Dont even get to try and send data. will Look at it again when I get home. i got a packet sniffer there and will be able to see the packet errors.

Udp is the basically the same

form_load
udp.localport = 0 ' lets system set port
udp.remotehost = "www.kurtsimmons.com"
udp.remoteport = 23
end sub

command1_click
udp.senddate "Username:Test"
end sub

udp_dataarrival
dim temp as string
udp.getdata temp
end sub
nothing comes back at all, will try with your code also tonight, Again when i get the packet sniffer.

[Edited by jtm7699 on 07-11-2000 at 11:36 AM]

got the data now, was an error in the name
will look at it some more

Thanks,

I noticed that seems to be the norm with UNIX servers on port 23. But notice that windows telnet handles it properly

Hey JTM you spelled kurtsimons.com wrong

yop i hacked your computer and it works , no im playing i dont hack out it works , col man what ever you did are you amking your own server or somthing whatrever man later

Kurt,
tried to convert the string out of ASC and only got a bunch of numbers. Will continue, Will see what the packet looks like coming back to the windows telnet and the packet coming back to winsock. Will also look at the packet going from the Telnet and the packet going from the Winsock. Should be able to look at it later Tonight. hope so. Now you have me interested.

I hit this problem a while ago on another unix server, never figured out what was wrong, but now I came across the problem on another system which made me realize it wasn't me or my equipment and that someone out there must have delt with this before.