Skip to content

Commit ea4c64f

Browse files
Court72Court72
authored
Merge pull request #92428 from MsGabsta/patch-1
Update what-is-ip-address-168-63-129-16.md
2 parents c9199ca + d226d93 commit ea4c64f

File tree

1 file changed

+94
-1
lines changed

1 file changed

+94
-1
lines changed

‎articles/virtual-network/what-is-ip-address-168-63-129-16.md

Lines changed: 94 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,100 @@ The public IP address 168.63.129.16 is used in all regions and all national clou
4343

4444
- When the VM is part of a load balancer backend pool, [health probe](../load-balancer/load-balancer-custom-probe-overview.md) communication should be allowed to originate from 168.63.129.16. The default network security group configuration has a rule that allows this communication. This rule leverages the [AzureLoadBalancer](../virtual-network/service-tags-overview.md#available-service-tags) service tag. If desired this traffic can be blocked by configuring the network security group however this will result in probes that fail.
4545

46+
## Troubleshoot connectivity
47+
### Windows OS
48+
You can test communication to 168.63.129.16 by using the following tests with PowerShell.
49+
50+
```
51+
Test-NetConnection -ComputerName 168.63.129.16 -Port 80
52+
Test-NetConnection -ComputerName 168.63.129.16 -Port 32526
53+
Invoke-RestMethod -Headers @{"Metadata"="true"} -Method GET -Uri http://168.63.129.16/?comp=versions
54+
```
55+
Results should return as shown below.
56+
57+
```
58+
Test-NetConnection -ComputerName 168.63.129.16 -Port 80
59+
ComputerName : 168.63.129.16
60+
RemoteAddress : 168.63.129.16
61+
RemotePort : 80
62+
InterfaceAlias : Ethernet
63+
SourceAddress : 10.0.0.4
64+
TcpTestSucceeded : True
65+
```
66+
67+
```
68+
Test-NetConnection -ComputerName 168.63.129.16 -Port 32526
69+
ComputerName : 168.63.129.16
70+
RemoteAddress : 168.63.129.16
71+
RemotePort : 32526
72+
InterfaceAlias : Ethernet
73+
SourceAddress : 10.0.0.4
74+
TcpTestSucceeded : True
75+
```
76+
77+
```
78+
Invoke-RestMethod -Headers @{"Metadata"="true"} -Method GET -Uri http://168.63.129.16/?comp=versions
79+
xml Versions
80+
--- --------
81+
version="1.0" encoding="utf-8" Versions
82+
```
83+
You can also test communication to 168.63.129.16 by using telnet or psping.
84+
85+
If successful, telnet should connect and the file that is created will be empty.
86+
87+
```
88+
telnet 168.63.129.16 80 >> C:\<<EDIT-DIRECTORY>>\168-63-129-16_test-port80.txt
89+
telnet 168.63.129.16 32526 >> C:\<<EDIT-DIRECTORY>>\168-63-129-16_test--port32526.txt
90+
```
91+
92+
```
93+
Psping 168.63.129.16:80 >> C:\<<EDIT-DIRECTORY>>\168-63-129-16_test--port80.txt
94+
Psping 168.63.129.16:32526 >> C:\<<EDIT-DIRECTORY>>\168-63-129-16_test-port32526.txt
95+
```
96+
### Linux OS
97+
On Linux, you can test communication to 168.63.129.16 by using the following tests.
98+
99+
```
100+
echo "Testing 80 168.63.129.16 Port 80" > 168-63-129-16_test.txt
101+
traceroute -T -p 80 168.63.129.16 >> 168-63-129-16_test.txt
102+
echo "Testing 80 168.63.129.16 Port 32526" >> 168-63-129-16_test.txt
103+
traceroute -T -p 32526 168.63.129.16 >> 168-63-129-16_test.txt
104+
echo "Test 168.63.129.16 Versions" >> 168-63-129-16_test.txt
105+
curl http://168.63.129.16/?comp=versions >> 168-63-129-16_test.txt
106+
```
107+
108+
Results inside 168-63-129-16_test.txt should return as shown below.
109+
110+
```
111+
traceroute -T -p 80 168.63.129.16
112+
traceroute to 168.63.129.16 (168.63.129.16), 30 hops max, 60 byte packets
113+
1 168.63.129.16 (168.63.129.16) 0.974 ms 1.085 ms 1.078 ms
114+
115+
traceroute -T -p 32526 168.63.129.16
116+
traceroute to 168.63.129.16 (168.63.129.16), 30 hops max, 60 byte packets
117+
1 168.63.129.16 (168.63.129.16) 0.883 ms 1.004 ms 1.010 ms
118+
119+
curl http://168.63.129.16/?comp=versions
120+
<?xml version="1.0" encoding="utf-8"?>
121+
<Versions>
122+
<Preferred>
123+
<Version>2015-04-05</Version>
124+
</Preferred>
125+
<Supported>
126+
<Version>2015-04-05</Version>
127+
<Version>2012-11-30</Version>
128+
<Version>2012-09-15</Version>
129+
<Version>2012-05-15</Version>
130+
<Version>2011-12-31</Version>
131+
<Version>2011-10-15</Version>
132+
<Version>2011-08-31</Version>
133+
<Version>2011-04-07</Version>
134+
<Version>2010-12-15</Version>
135+
<Version>2010-28-10</Version>
136+
</Supported>
137+
```
138+
46139
## Next steps
47140

48141
- [Security groups](./network-security-groups-overview.md)
49-
- [Create, change, or delete a network security group](manage-network-security-group.md)
142+
- [Create, change, or delete a network security group](manage-network-security-group.md)

0 commit comments

Comments
 (0)