Re: RWW Issues When Connecting from WAN Side

Tech-Archive recommends: Fix windows errors by optimizing your registry

Paul D. wrote:
Hi Joe,

To answer your question, from what I observed during my test I've concluded that if you:

1. netstat on the server before initiating the connect to client/server in RWW from a client, it returns nothing
2. netstat after clicking the connect to client/server link (but before logging in), it returns LISTENING
3. netstat after successfully logging in to client/server over RWW, it changes to ESTABLISHED
4. also, after a prolonged period of non-activity, it will change to FIN_WAIT_2 just prior to disconnecting the RWW client

I agree that it 'feels' as though something is being blocked, but I see no evidence in my firewall logs. I'm not running ISA - tried it once, had too many probs! I run a harware firewall instead. To answer your other question (good observation), the WIRELESS LAN client IPs are on a different subnet from that of the WIRED LAN clients.

This is definitely a weird one, I'll admit..

Any chance of the external client using the same 192.168.168 network? That would cause unpredictable results. If not, I think Network Monitor is the next stage, to see whether the expected TCP/IP conversation with the remote client is taking place, comparing it with a local one.
.

Relevant Pages