Open MuhammadHamzaChughtai opened 3 weeks ago
Hi Muhammad,
It seems that the script is failing to connect to your modem using telnet. So one of the following might be the cause,
A) Network/Firewall issue B) Telnet disabled on modem C) iDirect perhaps have removed telnet support in the latest firmware version
I don't have access to any iDirect modems anymore as I have changed jobs since I wrote this script so its hard for me to check cause C.
Can you open a telnet session to the modem from your PC? If so does that work?
Hi Fredde,
Thank you for replying to my query. I believe you're correct. It's a iDirect X1 modem, which we typically access via its LAN IP through a web browser using login credentials. I can access the modem's web interface and ping the LAN IP using CMD as well as PRTG. I suspect this might be due to Telnet, as I'm receiving a "connection refused" error when attempting through putty. I would appreciate it if you could provide some steps related to Telnet, as this might help in getting the script to run. However, I can't find any Telnet-related settings or configuration on the iDirect X1 modem's access page.
PS C:\Program Files (x86)\PRTG Network Monitor\Custom Sensors\EXEXML> C:\Program Files (x86)\PRTG Network Monitor\Custom Sensors\EXEXML\iDirect.ps1 New-Object : Exception calling ".ctor" with "2" argument(s): "A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 172.87.99.24:23" At C:\Program Files (x86)\PRTG Network Monitor\Custom Sensors\EXEXML\iDirect.ps1:18 char:15
<?xml version= 1.0 encoding=Windows-1252 ?>