Great Office - Hummig KG Posted February 12, 2009 Report Share Posted February 12, 2009 Dear Members, if I want to check if some service is running, I usually run telnet on the appropriate port (e. g. Webservice = 80, SMTP = 25 ...). I wonder, if TFTP is active on our server, because there is no response on Port 65 on the Server PBXnSIP is installed. Of course, the Port for TFTP is set to 65 in the setup. Question: Should I get any response, e. g. blank screen, when running "telnet localhost 65" (on the local machine, pbxnsip is installed) or what else does mean TFTP runs on port 65? Remark: I also get no response, on "telnet IP-of-the-Server 65"... Regards, Lucas Hummig Quote Link to comment Share on other sites More sharing options...
pbx support Posted February 12, 2009 Report Share Posted February 12, 2009 I do not think you would get any response from the TFTP. On a side note, you have to restart the PBX service if you changed the TFTP port from 69 (default) to 65. Dear Members, if I want to check if some service is running, I usually run telnet on the appropriate port (e. g. Webservice = 80, SMTP = 25 ...). I wonder, if TFTP is active on our server, because there is no response on Port 65 on the Server PBXnSIP is installed. Of course, the Port for TFTP is set to 65 in the setup. Question: Should I get any response, e. g. blank screen, when running "telnet localhost 65" (on the local machine, pbxnsip is installed) or what else does mean TFTP runs on port 65? Remark: I also get no response, on "telnet IP-of-the-Server 65"... Regards, Lucas Hummig Quote Link to comment Share on other sites More sharing options...
Great Office - Hummig KG Posted February 12, 2009 Author Report Share Posted February 12, 2009 PBX uses port is 69 as the default TFTP port. But if you have changed it 65, then you need to restart the PBX service. Thanks for the fast reply. Sorry, this was a type-mismatch. I didn't changed the port 69, but have restarted the PBX service several times, but still no answer on telnet 69. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted February 12, 2009 Report Share Posted February 12, 2009 Thanks for the fast reply. Sorry, this was a type-mismatch. I didn't changed the port 69, but have restarted the PBX service several times, but still no answer on telnet 69. TFTP is UDP, telnet is TCP. Check out "netstat" from the command line to see what ports the PBX uses. Quote Link to comment Share on other sites More sharing options...
Great Office - Hummig KG Posted February 12, 2009 Author Report Share Posted February 12, 2009 TFTP is UDP, telnet is TCP. Check out "netstat" from the command line to see what ports the PBX uses. Thank you so much. Netstats lists different ports, but nothing about the TFTP-Port 69... The "NTP-Port" below (in the System Administration) is empty and not described in the WIKI at the Port Setup. Does this cause the problem? Quote Link to comment Share on other sites More sharing options...
pbx support Posted February 13, 2009 Report Share Posted February 13, 2009 If you set the log level to 7 or above and restart the PBX, you would see whether the port 69 is being used or not. Check out the last 2 lines of the below output ***** 1] 2009/02/12 21:39:23: Starting up version 3.2.0.3144 [8] 2009/02/12 21:39:23: Found interface on 127.0.0.1 with netmask 255.0.0.0 [8] 2009/02/12 21:39:23: Found interface on 192.168.2.10 with netmask 255.255.255.0 [8] 2009/02/12 21:39:23: Found interface on fe80::f5e4:129f:3257:5b81 with netmask :: [8] 2009/02/12 21:39:23: Found interface on ::1 with netmask :: [7] 2009/02/12 21:39:24: Found time zones HST AKDT AKST PDT PST MDT MST CDT CST2 EDT EST ADT AST NDT NST BST CET GMT+2 GMT+3 CST CAT IST AUS1 AUS2 AUS3 AUS4 AUS5 AUS6 GMT [8] 2009/02/12 21:39:24: Timer frequency is 500 us [1] 2009/02/12 21:39:24: Working Directory is C:\Program Files\pbxnsip\PBX [7] 2009/02/12 21:39:24: UDP: Opening socket [7] 2009/02/12 21:39:24: UDPv6: Opening socket [5] 2009/02/12 21:39:24: Starting threads [7] 2009/02/12 21:39:24: UDP: Opening socket [7] 2009/02/12 21:39:24: UDPv6: Opening socket [7] 2009/02/12 21:39:24: UDP: Opening socket on port 5060 [7] 2009/02/12 21:39:24: UDPv6: Opening socket on port 5060 [7] 2009/02/12 21:39:24: TCP: Opening socket on port 5060 [7] 2009/02/12 21:39:24: TCPv6: Opening socket on port 5060 [7] 2009/02/12 21:39:24: TCP: Opening socket on port 5061 [7] 2009/02/12 21:39:24: TCPv6: Opening socket on port 5061 [5] 2009/02/12 21:39:24: Set processor affinity to 1 [7] 2009/02/12 21:39:24: TCP: Opening socket on port 80 [7] 2009/02/12 21:39:24: TCPv6: Opening socket on port 80 [7] 2009/02/12 21:39:24: TCP: Opening socket on port 443 [7] 2009/02/12 21:39:24: TCPv6: Opening socket on port 443 [7] 2009/02/12 21:39:24: UDP: Opening socket on port 161 [7] 2009/02/12 21:39:24: UDPv6: Opening socket on port 161 [7] 2009/02/12 21:39:24: UDP: Opening socket on port 69 [7] 2009/02/12 21:39:24: UDPv6: Opening socket on port 69 *********** Thank you so much. Netstats lists different ports, but nothing about the TFTP-Port 69... The "NTP-Port" below (in the System Administration) is empty and not described in the WIKI at the Port Setup. Does this cause the problem? Quote Link to comment Share on other sites More sharing options...
andrewgroup Posted February 13, 2009 Report Share Posted February 13, 2009 from another PC run any of the free TFTP clients.....Run Wireshark in the process....TFTP lies dormant until a request is made... No Firewalls on the PBX please. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.