cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1923
Views
0
Helpful
2
Replies

Waas issue - Windows based connections

iprojetos
Level 1
Level 1

Hi All

i´m having some problems with Windows based connections in specific ports.

I can see in the connections statistics that ports 445, 3628, 135, 138, 139 and 389 presents the follow error: PT AD Int Error

172.20.1.119:4304     172.20.221.3:135      N/A               PT AD Int Error  

172.20.203.3:139      172.20.1.138:3288     N/A               PT AD Int Error  

172.20.203.3:445      172.20.1.138:3222     N/A               PT In Progress   

172.20.221.3:135      172.20.1.119:4304     N/A               PT AD Int Error  

172.20.203.3:445      172.20.1.138:3287     N/A               PT AD Int Error  

172.20.140.3:445      172.20.1.138:3965     N/A               PT In Progress   

172.20.1.15:1761      172.20.223.208:135    N/A               PT AD Int Error  

172.20.221.3:445      172.20.1.138:2441     N/A               PT In Progress   

172.20.223.208:135    172.20.1.15:1761      N/A               PT AD Int Error  

172.20.1.138:2441     172.20.221.3:445      N/A               PT In Progress   

172.20.203.3:139      172.20.1.138:3323     N/A               PT AD Int Error  

172.20.1.138:3320     172.20.203.3:445      N/A               PT AD Int Error  

172.20.1.138:3288     172.20.203.3:139      N/A               PT AD Int Error  

172.20.1.138:3287     172.20.203.3:445      N/A               PT AD Int Error  

172.20.1.138:3965     172.20.140.3:445      N/A               PT In Progress   

172.20.203.3:445      172.20.1.138:3320     N/A               PT AD Int Error  

172.20.1.138:3222     172.20.203.3:445      N/A               PT In Progress   

172.20.1.138:3323     172.20.203.3:139      N/A               PT AD Int Error  

I could see that only this ports are having this issue, all others like http, ftp, telnet, etc are working properly.

131385  172.20.221.214:58560         172.20.1.2:23 00:27:0d:79:bf:f5 TDL   79.5%

131490  172.20.221.236:63206       172.20.1.8:1478 00:27:0d:79:bf:f5 TDL   42.6%

132074   172.20.140.201:2815         172.20.1.2:23 00:21:55:86:5d:7f TDL   79.3%

133183  172.20.221.224:59050         172.20.1.2:23 00:27:0d:79:bf:f5 TDL   79.3%

133214   172.20.140.204:1447    172.20.1.251:49155 00:21:55:86:5d:7f TDL   00.0%

134779  172.20.221.216:53178         172.20.1.2:23 00:27:0d:79:bf:f5 TDL   76.9%

135557  172.20.223.240:52520         172.20.1.2:23 00:1e:7a:80:e5:b3 TDL   71.7%

136555  172.20.221.232:62504     172.20.1.253:1477 00:27:0d:79:bf:f5 TDL   64.4%

137337  172.20.221.237:59402         172.20.1.2:23 00:27:0d:79:bf:f5 TDL   71.6%

145220   172.20.140.201:2963       172.20.1.176:80 00:21:55:86:5d:7f TDL   03.9%

145222  172.20.221.214:58749       172.20.1.176:80 00:27:0d:79:bf:f5 TDL   40.4%

145228   172.20.140.206:1495      172.20.1.29:8080 00:21:55:86:5d:7f TDL   49.6%

145230   172.20.140.203:1443      172.20.1.29:8080 00:21:55:86:5d:7f TDL   49.9%

145231  172.20.203.209:61992       172.20.1.176:80 00:1e:7a:80:e5:b1 TDL   95.9%

145233    172.20.0.248:60972      172.20.223.3:135 00:1e:7a:80:e5:b3 TDL   03.3%

145281    172.20.223.3:56138       172.20.1.4:1026 00:1e:7a:80:e5:b3 TDL   00.0%

145313       172.20.1.4:4828    172.20.203.3:57432 00:1e:7a:80:e5:b1 TDL   33.6%

145340    172.20.0.244:56237      172.20.221.3:135 00:27:0d:79:bf:f5 TDL   00.0%

145341    172.20.0.244:56238    172.20.221.3:51799 00:27:0d:79:bf:f5 TDL   00.0%

Can anyone help me?

Thanks a lot.

Claudio Oliveira

1 Accepted Solution

Accepted Solutions

Nicolas Fournier
Cisco Employee
Cisco Employee

Hi Claudio,

This "PT AD Int Error" state can have multiple root causes so it will be difficult to pinpoint it like this.

It is most of the time a device on the path between the Edge and Core WAE which is modifying the TCP header preventing auto-discovery to succeed but it could be also a WAAS software internal error.

Could you check the devices on the path between your WAEs and see if any of those would modify the packets targeted to the ports you mentioned?

If you don't find any, I would advise you to open a TAC case to have this investigated as it will most then likely require the collection of a sysreport with transaction logging enabled.

Regards,

Nicolas

View solution in original post

2 Replies 2

Nicolas Fournier
Cisco Employee
Cisco Employee

Hi Claudio,

This "PT AD Int Error" state can have multiple root causes so it will be difficult to pinpoint it like this.

It is most of the time a device on the path between the Edge and Core WAE which is modifying the TCP header preventing auto-discovery to succeed but it could be also a WAAS software internal error.

Could you check the devices on the path between your WAEs and see if any of those would modify the packets targeted to the ports you mentioned?

If you don't find any, I would advise you to open a TAC case to have this investigated as it will most then likely require the collection of a sysreport with transaction logging enabled.

Regards,

Nicolas

Hi Nicolas.

Thanks for answer.

I looked device by device in the path and i didn´t found anything that could modify this packets. I really belive that is a BUG or Hardware issue, because i have the same structure in other customers and is working fine.

I will open a TAC case.

Thank you.

Regards

Claudio