Accepted Solutions
Hey @Sunnywaygis
Along with George's response, I have a PowerShell script that lets you check the ports as well, this does not require a device listening on that port as it temporarily places one in. This lets you run a command such as:
netstat -an | findstr :7443
Which allows you to find the port that you have active, if nothing is listening on that port, then you will not get a response.
PowerShell script:
$port = Read-Host "Enter Port Number"
$listener = [System.Net.Sockets.TcpListener]::new([System.Net.IPAddress]::Any, $port)
$listener.Start()
Write-Host "Listening on port $port..."
# Script will need to continue running to enable listener
try {
while ($true) {
$client = $listener.AcceptTcpClient()
$stream = $client.GetStream()
$reader = [System.IO.StreamReader]::new($stream)
$writer = [System.IO.StreamWriter]::new($stream)
# Reads any incoming data, optional use, Test-NetConnection will send blank data
$data = $reader.ReadLine()
Write-Host "Received data: $data"
# Optional response to data
$writer.WriteLine("Connection works, data received")
# Close the connection
$client.Close()
}
}
finally {
$listener.Stop()
}
For your question about the SSL certificates, you do not need to have one in order to get your Portal up and going, that is what I did in order to enable HTTP using a self-signed certificate. As George said, you will be better off if you start with a CA signed certificate immediately.
Cody
Hey @Sunnywaygis
Along with George's response, I have a PowerShell script that lets you check the ports as well, this does not require a device listening on that port as it temporarily places one in. This lets you run a command such as:
netstat -an | findstr :7443
Which allows you to find the port that you have active, if nothing is listening on that port, then you will not get a response.
PowerShell script:
$port = Read-Host "Enter Port Number"
$listener = [System.Net.Sockets.TcpListener]::new([System.Net.IPAddress]::Any, $port)
$listener.Start()
Write-Host "Listening on port $port..."
# Script will need to continue running to enable listener
try {
while ($true) {
$client = $listener.AcceptTcpClient()
$stream = $client.GetStream()
$reader = [System.IO.StreamReader]::new($stream)
$writer = [System.IO.StreamWriter]::new($stream)
# Reads any incoming data, optional use, Test-NetConnection will send blank data
$data = $reader.ReadLine()
Write-Host "Received data: $data"
# Optional response to data
$writer.WriteLine("Connection works, data received")
# Close the connection
$client.Close()
}
}
finally {
$listener.Stop()
}
For your question about the SSL certificates, you do not need to have one in order to get your Portal up and going, that is what I did in order to enable HTTP using a self-signed certificate. As George said, you will be better off if you start with a CA signed certificate immediately.
Cody
