Re: RWW Issues When Connecting from WAN Side
- From: Paul D. <PaulD@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 10 Jan 2008 08:29:02 -0800
Wireshark LAN/WAN Test Results:
LAN (XP Pro Client connecting to Server via RWW)
- Lots of traffic on TCP port 4125
- No traffic on TCP/UDP ports 3389
- Traffic on TCP port 443
WAN (XP Pro Client trying to connect to Server/Client via RWW)
- No traffic on TCP port 4125
- No traffic on TCP/UDP ports 3389
- Traffic on TCP port 443
Observations:
RWW client logs into http://server/remote, which creates port 443 traffic.
When RWW client successfully 'connects' to a server/client computer, traffic
should show up on TCP 4125. This happens for LAN RWW client, but is not
happening for WAN RWW client. Strangely, no traffic is showing up on either
TCP or UDP ports 3389 once an RWW session is established. According to Shawn
(MSFT) there should be traffic here. Dunno? So the question really is "what
is preventing WAN RWW clients from connecting? Firewall rules, DNS, WINS, XP
Client Windows Firewall rules - everything looks fine. Back to square A
again.. :[
--
Thanks,
Paul D.
MCP
"Joe" wrote:
Paul D. wrote:.
No chance of external IP conflicts - using non-routable (internal) IPs on the
LAN (different from those in my example). Afraid I'm not too savvy with
Network Monitor. Any recommendations on how best to use the tool to diagnose
the situation?
It just collects network traffic. All of it, including ARP broadcasts.
You then filter by IP/MAC/whatever to get the stuff you're interested
in. It may not be installed, as it isn't by default, you may need to add
it as a Windows Component, under Management and Monitoring Tools, and it
appears in Administrative Tools. It's reasonably intuitive to use. In
this case, start the capture, connect and disconnect a local RWW
session, stop the capture and view. Save the capture, then do the same
from an outside connection and compare them. Presumably something will
be missing from the outside attempt, but if we knew what, we could fix
it now.
I prefer Wireshark (formerly Ethereal), but that's an Open Source
program, which I wouldn't take responsibility for advising other people
to use on a server. Microsoft stuff should be safe.
- Follow-Ups:
- Re: RWW Issues When Connecting from WAN Side
- From: "Shawn Shao [MSFT]"
- Re: RWW Issues When Connecting from WAN Side
- References:
- Prev by Date: Re: Issues with store.exe and RPCServ.exe
- Next by Date: Re: Backup Configuration
- Previous by thread: Re: RWW Issues When Connecting from WAN Side
- Next by thread: Re: RWW Issues When Connecting from WAN Side
- Index(es):
Relevant Pages
|
