Creating a wedge between a UO Server and UO client using VB.NET and The Winsock COM

[pex]

My network programming background comes from VB 6.0 and the Winsock Common Control. When VB.NET came out, I moved to that for network programming.

I'm going to hit up C# and System.Net.Sockets eventually, but for now I'm having issues implementing my wedge program with VB.NET and Winsock:

The current issue is that I can make socket connections between the Login Client, the Login Server, the Game Client, and the Game Server (I think?) but I have trouble creating the Game Server connection or, if I preemptively connect to the game server (which I could never do in a real life setting as I have to parse the server info from the server redirect packet), I am only connected for a short period of time before being disconnected.

I have a class library that handles all the winsock garbage, and then a windows application for the interface. Something that bothers me is that I have a method in my class, called "pollSockets()" which returns the socket states of all four sockets, but if I poll these sockets for their states when I have issues sending packets, the state I get from the poll is not the same as I get when I test elsewhere). (I frequently call the method via timer on my form.)

Source available on request. I was just wondering if anyone had experience with simple UO VB6/VB.NET sockets programming that could mention what might be the issue.

The whole program is really as simple as 'take the packet from the source, pass it to the destination.' I really don't think this should be a big deal.

My testing programs:
UO client 2.0.3 (both encrypted and unencrypted, to see what the packets are I use unencrypted)
SPHERE 55i

Writing in Visual Studio 2003.

(I can connect to SPHERE 55i using the unencrypted client for periods of time so this is not the issue.)

[pex]

Clarification:
I can run a server on my local machine and can connect fine.
I cannot connect to the game server of a remote server.