2回答
- 新しい順
- 投票が多い順
- コメントが多い順
0
Hello. Thank you for writing to us. Looking at the events, it appears to be an issue at the Network level. We will suggest to check if you have any proxy server is enabled and causing the issue. Please consider to run the following commands:
- Execute the following command to see if "TcpTestSucceeded" is True": Test-NetConnection -ComputerName "Replace with Windows powershell endpoint of FSx" -Port 5985
- Check if 'Test-WSMan' is successful or not: Test-WSMan -ComputerName "Replace with Windows powershell endpoint of FSx"
- If the above commands fails, then execute the following to check if proxy is set: netsh winhttp show proxy
- If proxy is found then execute the following command to reset it (do make note of the proxy settings from step 3 before resetting): netsh winhttp reset proxy
- After resetting, please execute the command from step 2 and it should work this time.
Check if the software is able to fetch the desired output of free space for FSx now.
Please mark this response as "Answer" if it helped to resolve the issue.
回答済み 7ヶ月前
0
Thanks for your reply.
Test-NetConnection -Port 445 ==> True
Test-NetConnection -Port 5985 ==> False
netsh winhttp show proxy => Direct access (no proxy server)
As a note: I temporarily allowed all traffic between source machine and FSX, although there are already discrete rules for 445 and 5985.
回答済み 7ヶ月前
関連するコンテンツ
- 質問済み 6年前
Thanks for your reply.
Test-NetConnection -Port 445 ==> True
Test-NetConnection -Port 5985 ==> False
netsh winhttp show proxy => Direct access (no proxy server)
As a note: I temporarily allowed all traffic between source machine and FSX, although there are already discrete rules for 445 and 5985.