Skip to content

Commit 2640ffb

Browse files
committed
Learn Editor: Update service-bus-troubleshooting-guide.md
1 parent 869da03 commit 2640ffb

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/service-bus-messaging/service-bus-troubleshooting-guide.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -181,13 +181,13 @@ The following steps help you with troubleshooting connectivity/certificate/timeo
181181
```
182182
- Run the following command to check if any port is blocked on the firewall. Ports used are 443 (HTTPS), 5671 and 5672 (AMQP) and 9354 (Net Messaging/SBMP). Depending on the library you use, other ports are also used. Here's the sample command that check whether the 5671 port is blocked.
183183

184-
```powershell
184+
```powershell
185185
tnc <yournamespacename>.servicebus.windows.net -port 5671
186186
```
187187

188-
On Linux:
188+
On Linux:
189189

190-
```shell
190+
```shell
191191
telnet <yournamespacename>.servicebus.windows.net 5671
192192
```
193193
- When there are intermittent connectivity issues, run the following command to check if there are any dropped packets. This command tries to establish 25 different TCP connections every 1 second with the service. Then, you can check how many of them succeeded/failed and also see TCP connection latency. You can download the `psping` tool from [here](/sysinternals/downloads/psping).

0 commit comments

Comments
 (0)