Skip to content

Commit e61f94d

Browse files
authored
Merge pull request #101418 from spelluru/troubleshoot0116
Feedback from Wagner and Jaganathan
2 parents c6d1353 + e0637b6 commit e61f94d

File tree

2 files changed

+5
-5
lines changed

2 files changed

+5
-5
lines changed

articles/event-hubs/event-hubs-messaging-exceptions.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.topic: article
1212
ms.tgt_pltfrm: na
1313
ms.workload: na
1414
ms.custom: seodec18
15-
ms.date: 12/03/2019
15+
ms.date: 01/16/2020
1616
ms.author: shvija
1717

1818
---
@@ -114,10 +114,10 @@ The following steps may help you with troubleshooting connectivity/certificate/t
114114
```shell
115115
telnet sbwagn2.servicebus.windows.net 5671
116116
```
117-
- When there are intermittent connectivity issues, run the following command to check if there are any dropped packets. Keep it running for approximately 1 minute to know if the connections are partially blocked. You can download the `psping` tool from [here](/sysinternals/downloads/psping).
117+
- When there are intermittent connectivity issues, run the following command to check if there are any dropped packets. This command will try to establish 25 different TCP connections every 1 second with the service then you can check how many succeeded/failed and also see TCP connection latency. You can download the `psping` tool from [here](/sysinternals/downloads/psping).
118118
119119
```shell
120-
psping.exe -t -q ehedhdev.servicebus.windows.net:9354 -nobanner
120+
.\psping.exe -n 25 -i 1 -q yournamespace.servicebus.windows.net:5671 -nobanner
121121
```
122122
You can use equivalent commands if you're using other tools such as `tnc`, `ping`, and so on.
123123
- Obtain a network trace if the previous steps don't help and analyze it or contact [Microsoft Support](https://support.microsoft.com/).

articles/service-bus-messaging/service-bus-messaging-exceptions.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -119,10 +119,10 @@ The following steps may help you with troubleshooting connectivity/certificate/t
119119
```shell
120120
telnet sbwagn2.servicebus.windows.net 5671
121121
```
122-
- When there are intermittent connectivity issues, run the following command to check if there are any dropped packets. Keep it running for approximately 1 minute to know if the connections are partially blocked. You can download the `psping` tool from [here](/sysinternals/downloads/psping).
122+
- When there are intermittent connectivity issues, run the following command to check if there are any dropped packets. This command will try to establish 25 different TCP connections every 1 second with the service then you can check how many succeeded/failed and also see TCP connection latency. You can download the `psping` tool from [here](/sysinternals/downloads/psping).
123123
124124
```shell
125-
psping.exe -t -q ehedhdev.servicebus.windows.net:9354 -nobanner
125+
.\psping.exe -n 25 -i 1 -q yournamespace.servicebus.windows.net:5671 -nobanner
126126
```
127127
You can use equivalent commands if you're using other tools such as `tnc`, `ping`, and so on.
128128
- Obtain a network trace if the previous steps don't help and analyze it or contact [Microsoft Support](https://support.microsoft.com/).

0 commit comments

Comments
 (0)