Thanks for the advice. I'm moderately certain that the firewall is not the issue, because I've used a protocol analyzer to capture the packets between the stations, but I'll give that a try.
Just to provide some additional information: The TCP conversation starts up fine, which indicates that the firewall is letting the packets through. Media Center (the client) sends a packet containing:
GET /Connect?v=3 HTTP/1.1..Accept: */*..Icy-MetaData: 1..User-Agent: JRiver Internet Reader/2.0..Host: 192.168.1.11:42000..Connection: Keep-Alive..Cache-Control: no-cache....
Then Media Server sends a packet containing:
HTTP/1.1
Then Media Server sends a packet containing:
200 OK..Date: Tue, 20 May 2003 00:56:32 GMT..Content-Type: text/plain..Cache-Control: no-cache..Connection: close....
The third and final packet closes the TCP connection. Then Media Center (the client) opens a second TCP connection and downloads the library. When I connect to the non-working server, the conversation simply stops after the second packet. The third packet doesn't come from Media Server.
What makes this so strange is that I uninstalled and reinstalled cleanly to make sure everything was at the same version, I checked the MD5 hash of the Media Server executable to make sure it really was the same on all machines... as far as I can tell, everything is identical on the working and non-working machines.
I expect that this is probably related to something weird on the non-working machine, maybe not to Media Server itself, but I hoped that maybe somebody with more insight into the code could tell me where things are breaking down.
Thanks again for the suggestions...
Joshua