Trying to learn the absolute basics of Winsock in VB6.0.

I downloaded the example found here:

http://www.planetsourcecode.com/vb/scripts/ShowCode.asp?txtCodeId=69402&lngWId=1

It works if I run both the server and client on my own desktop (naturally), but I tried it with a friend and it simply will not work. In the Client program, I had him type in my IP address, which I got from

http://whatismyipaddress.com/

and it will not run. It is listed as an exception my windows firewall (allowed it through) and the port numbers are correct.

Any ideas?

8/20/2008 9:57:41 PM

i'd stick wireshark/winpcap on your nic and see if the traffic is actually getting through to you or not first

if it is, look in the packet data to see what the client/server responses are and where they are failing

if you're doing anything related to network stacks or network communication in general, a sniffer is an invaluable tool.

if you're not comfortable with analyzing traces, i'll take a quick look at the capture if you'd like.

8/20/2008 10:16:46 PM

I have enabled port forward as appropriate. Still no fucking dice. This is maddening.

8/20/2008 10:51:13 PM

Last thing:
I have put captures of my ipconfig and the before and after states of my router's port forwarding config screen here:
http://cynicmallow.bravehost.com/pics.html

(yes, I tested on port 300)

8/20/2008 11:26:00 PM

do this:

1) install wireshark and winpcap. http://prdownloads.sourceforge.net/wireshark/wireshark-setup-1.0.2.exe

2) open wireshark, start a capture (click the interfaces button, find your nic, click the Start button next to it)

3) initiate communications between your client app and server app. do it a couple of times.

4) stop the capture.

5) save the capture somewhere. it should have pcap as its extension.

6) PM me when you've got this.

edit: before you do the above - looking at the screencaps you posted... the "enable" checkbox isn't checked next to the forwarding rule you created for port 300... did you make sure to check that?

8/21/2008 1:29:32 AM

I've written several applications using Winsock with VB6 including an AIM client. However, I'd recommend moving to VB.NET if it is at all feasible.

8/21/2008 1:41:24 AM

i'd recommend moving away from visual basic all together.

8/21/2008 1:42:35 AM

There is nothing wrong with VB.NET, or even legacy VB for that matter.

8/21/2008 1:49:48 AM

as a legitimate application development platform, vb and vb.net are somewhat lacking

for one-offs and proof-of-concept/RAD, vb is fine. that's what it was made for.

there's a reason why the vast majority of substantial commercial apps aren't written in vb.

8/21/2008 2:02:04 AM

Quote :

"the "enable" checkbox isn't checked next to the forwarding rule you created for port 300... did you make sure to check that? "

Saw that too. Yeah, I did. Same results. Will try wireshark and such when I can. Thanks.

Quote :

"for one-offs and proof-of-concept/RAD, vb is fine."

That's really all I'm doing. I'm (clearly) no developer or anything.

8/21/2008 8:16:48 AM

^^ It's true that few off-the-shelf applications are written in VB, but many companies use VB to develop in-house applications. What is it you think VB.NET is lacking? (Keep in mind it can do anything any other .NET language can do.) Then tell me why these limitations should cause a developer to give up on VB.NET and use something else.

8/21/2008 11:54:58 AM

Hooked up to the cable modem via ethernet and tested. Works fine.

...wait, basic question. My IP while on the router is 216.36.xx.xx (http://whatismyipaddress.com/). Running ipconfig says it's 192.168.1.100, which I thought was only a local address. How is an incoming connection ever supposed to find my machine if my IPv4 to the world is 192.168.1.100?

[Edited on August 25, 2008 at 8:54 PM. Reason : ]

[Edited on August 25, 2008 at 8:56 PM. Reason : ]

8/25/2008 8:42:32 PM

Got it.

/thread

8/25/2008 9:36:44 PM

freakin network n00bs

8/26/2008 8:48:13 PM