04-25-2007 02:05 PM
Can somebody elaborate more on the following:
10.182.2.130:27385 161.141.105.217:139 Internal Server
10.182.2.130:20814 10.220.3.150:139 Internal Server
10.182.2.130:26997 161.141.105.217:445 Internal Server
10.182.2.130:18271 10.220.3.75:445 Internal Server
10.182.2.130:22309 10.220.139.150:445 Internal Server
10.182.2.130:60711 10.220.136.21:139 Internal Server
10.182.2.130:15729 10.179.12.91:139 App Dyn Mtch Non-Optimized
What it means by Interal Server and Non-Optimized under the pass-through connections. If this is a problem what would be the direction for a resolution. All I see are ports 139 and 445.
04-26-2007 10:06 AM
George,
The 'Internal Server' designation means that the connection was initiated from an internal server process within the WAE. An example of this would be the WAFS AO performing CIFS server auto-discovery.
The 'App Dyn Mtch Non-Optimized' designation means that the connection has been forced via an dynamic policy match to be accounted for as non-optimized, even though the connection may be optimized.
Is 10.182.2.130 one of your WAE devices running the WAFS Edge or Core service?
Zach
04-26-2007 11:39 AM
Zach,
My question now is how would I optimize those internal connections? The 10.182.2.130 is running both as an Edge and Core.
04-26-2007 10:25 PM
George,
Does another WAE exist between 10.182.2.130 and the IP addresses listed in the output?
Zach
04-30-2007 07:02 AM
Zach,
Yes there is another WAE that exists between the output that I listed.
05-02-2007 08:53 PM
If 10.182.2.130 is running the WAFS Core service, it could be traffic related to CIFS auto-discovery. Can you provide some additional information about the topology?
Thanks,
Zach
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide