Odd sockets problem?

["Brad Stone" <brad@xxxxxxxxxxxx>]

Ok, here's the scoop.

I have a customer using my GETURI utility to work with web
services.  He is testing on some IntrAnet services.

He says he has 2 enviroments set up.  One on port 8080
which is a test environment, and one on ports 8081 and 80
which are production.

>From a web browser, if he specifies port 8080 or 8081, he
gets the right server.

But from GETURI, he says if he uses port 8080 or port 8081,
he always gets a response back from the 8081 (prod) box.

I had him place a static document on each server.  The test
one said TEST, the Prod one said PROD.  He tested with the
browser, and got the appropriate document.

He then tested with GETURI, and always got the PROD
document no matter if he specified 8080 or 8081 for the
port number.

I've tripled checked the source, debugged, and couldn't
find any way that the port could be getting changed.

I also had him test on my web site on port 80 and port 8080
which should reveal different results.  Port 80 worked
fine, port 8080 resulted in no connection, most likely
because their firewall is blocking that port (which then
proves that the port GETURI was using works fine).  He got
the same results on his browser.

I'm really pulling my hair out on this one.  I've got
hundreds of users using this without this problem, so I'm
leaning towards some sort of odd web server config (they
are running all websphere servers) or networking problem.
 But I'm running out of ideas on where to look. 

What would cause his browser and GETURI (which uses sockets
APIS) to act differently?    Thanks for any ideas...  I
know there are a lot out there with more netorking know how
than me that could offer possible ideas.