Telnet cannot connect

Hi, i have a strange problem with my cisco 837. I can telnet to it from my local lan no problems but when i try to telnet to it from work or any external ip it will not and eventually times out. I did have an access list applied to the vty lines but i allowed my work ip address and could see the match counter increment on the allow statement. I have now completely removed the access list but the problem remains.
Trying 82.12.xxx.xxx...
telnet: connect to address 82.12.xxx.xxx: Connection timed out
line vty 0 4
session-timeout 35791
exec-timeout 35791 0
logging synchronous
length 0
transport preferred telnet
transport input telnet ssh
transport output all

took me a little while but figured it out. I had my internet connected nat'd, the route map pointed to an access list which said permit ip any any. This was causing the remote telnet/ssh problems. The nat access list needed to be for the inside networks permited only i.e. something like permit 192.168.1.0 0.0.0.255 any.

Similar Messages

Telnet cannot connect to port = 6020

Hi,
I have Sun os 5.1, i cannot connect by telnet using port number 6020 from my laptop!!
my command used from my lap top is : telnet myIP 6020
result : cannot connect to.........
any ideas...
thkxs.

Ok, I rechecked my router page by page and have found one solution .. .the https management page of the router defaults to 443 - so have changed that to 4443, rebooted router and can now access my http://mydomain/owa - so that is good. However, still
cannot telnet to port 25 on the exchange server from external. The port forwarding is definitely correct for port 25.
I have rechecked the receive connector: MAIL FLOW - RECEIVE CONNECTORS - DEFAULT FRONTEND SERVER
and under security - anoymous users is checked. That SHOULD let me connect yes? But it does not.
Where else does this need to be changed - can you advise?
regards
steve

Telnet cannot connect to Remote Computer

When I telnet my localhost it works completely fine..
But It's not able to connect to Remote Host
It says Unable to Connect to Remote Host, Operation Timed Out
But my Remote Laptop is able to connect to this system perfectly...
I don't understand where's the issue.
Any Help ??

Do you mean, you can access the target computer using the other computer and not the
one you’re on right now? Can you ping the target computer using that computer
and vice versa? Just make sure that the computers are pinging each other to
ensure that they are communicating.

Macbook Pro Cannot Connect to SMTP

I am running a 2010 MacBook Pro with OS X 10.6.8. I use Mac Mail app to send and receive e-mail. Since Thursday 27th Dec 2012 I have been unable to send e-mail. I get the grey spinning wheel until the following error message appears:
The SMTP connection to server “mail.(mydomain).co.uk” failed.
My outgoing mail server is currently showing as offline. In fact I have 2 e-mail accounts and both are showing as offline. No problem receiving mail. Connection doctor connects fine to incoming mail, but not outgoing.
I have tried the following (plus other things) without any success:
Checked all the details, passwords etc
Changed ports from 25 to 465 and 587
Checked my IP address - it is not blacklisted
Removed and re-added e-mail account
Telnet port 25 - it is not blocked, but appeared to successfully connect (from what I understood from checking www)
Temporarily disabled firewall
Re-installed Mac app
Rebuilt mailbox
Repaired disk permissions
Used the repair disk utility
Deselected SSL and changed various options within "Edit SMTP server list"
Reset the keychain
Tried updating software but it says no update available.
Re-instated an old Accounts.plist (and one other file which I forget, something like com.apple.mail) from time capsule.
I then set up a hotmail account on Mail app but had exactly the same problem, ie cannot connect with SMTP server.
However, I set up my e-mail account on my wife's iPad with the same details and there was no problem at all, e-mail sent just fine as it does from my iPhone. So the issue has to be with my Macbook, right? Can anyone help before I go and spent £1250 on a new Macbook? I'm sure I'm missing something obvious. Thanks in advance for any advice.

Just FYI, I've had the same problem for months now. I have been accessing my hotmail via the web, but decided to try the OS X Mail app. I could get emails into the account with no problem but couldn't send. I read all the blog and support entries and have tried everything they recommended, like changing my computer name to one word, without success. Then last night, it just so happened that my broadband provider had to change out my wireless modem. As soon as he plugged in the new one, some emails that had been in my outbasket for a month went through instantly and all of a sudden my Mail, both incoming and outgoing now work. So I think people need to look at their router settings for the a solution to the problem.

Cannot connect to ASDM on ASA 5505 over https

Problem: Cannot connect to ASDM on ASA 5505 when vlan1 network is changed from the factory default.
Hi all. I am just getting started on a new ASA 5505, working it in a test lab environment. I ran thru the initial setup wizard. During that time I specified a name for Vlan1 (changed from 'inside' to 'INTR-NET'), modified the Vlan1 IP address to use DHCP, and then populated the Device Config Access table with entries corresponding to the entire Class B network here on the local intranet. I don't recall if the factory-default network was already populated, but if it wasn't I added it as 192.168.1.0/255.255.255.0
I then saved the config, and verified that the ASA got a dhcp address using the RS-232 console. I then reconfigured the laptop I have plugged into port 0/1 with it's normal address on the intranet and discovered that I couldn't reconnect to ASDM. The ASDM client times out, and a web browser opened to https://(ASA5505's dhcp addr) fails as well.
I then used the console to add another http IP address matching the specific IP address (xxx.240.113.129/255.255.255.255) which the laptop is set for, to the list of permissible admin connections, but saw no difference.
This issue is much the same as was reported in this prior forum posting:
http://forums.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Security&topic=General&topicID=.ee6e1f8&CommCmd=MB%3Fcmd%3Dpass_through%26location%3Doutline%40%5E1%40%40.2cc16cb8/4
EXCEPT that I was already aware the admin IP address(es) needed to be registered to enable access via SSH/Telnet/HTTPS.
And, I did that step, but it is not working. I have tried adding various combinations of network ranges in the device config access list, including the specific subnet that the lab's dhcp server assigned to the ASA 5505 (xxx.240.112.0/255.255.254.0), but there is no difference. I can traceroute to the laptop and ping the Vlan1 interface from the laptop, but the https ASDM (and ssh connections too) are not successful. This is very frustrating.
The device is brand new, I see that upon boot it loads asa724-k8.bin, and the software banner says Cisco Adaptive Security Appliance Software Version 7.2(4)
Note also that, from the RS-232 console, if I reset the IP address to the static, factory default (192.168.1.1) and manually config my laptop on the same subnet, then ASDM makes the connection. Just like out of the box. But when I put it back onto our intranet and verify the DHCP lease, then ASDM is a no go.
Can you think of what I've missed?

Good question. Let me add that info plus related Vlan config details:
ASA5505A# show ip
System IP Addresses:
Interface Name IP address Subnet mask Method
Vlan1 INTR-NET XXX.240.112.92 255.255.254.0 DHCP
Vlan2 VoIP 172.26.99.1 255.255.255.0 manual
Vlan3 dmz-unused 192.168.99.1 255.255.255.0 manual
Current IP Addresses:
Interface Name IP address Subnet mask Method
Vlan1 INTR-NET XXX.240.112.92 255.255.254.0 DHCP
Vlan2 VoIP 172.26.99.1 255.255.255.0 manual
Vlan3 dmz-unused 192.168.99.1 255.255.255.0 manual
ASA5505A# show switch vlan
VLAN Name Status Ports
1 INTR-NET up Et0/1, Et0/2, Et0/3, Et0/4
2 VoIP down Et0/5, Et0/6, Et0/7
3 dmz-unused down Et0/0
ASA5505A#
ASA5505A# config t
ASA5505A(config)# show running-config http
http server enable
http XXX.240.0.0 255.255.0.0 INTR-NET
http 192.168.1.0 255.255.255.0 INTR-NET
http XXX.240.113.129 255.255.255.255 INTR-NET
ASA5505A(config)#
ASA5505A(config)# show running-config ssh
ssh 192.168.1.0 255.255.255.0 INTR-NET
ssh XXX.240.0.0 255.255.0.0 INTR-NET
ssh timeout 5
SECURITY LEVEL IS 100 ON Vlan1 and Vlan2, 50 on Vlan3, and traffic is restricted from Vlan3 to Vlan1 because this is the basic license.

"Cannot connect to the iTunes Store" when using WiFi and Cisco VPN

hi
I'm on iPhone software 2.0 and have a connection to the internet via WiFi and VPN (using the integrated Cisco client). Everything works fine (Safari, Mail, mobileme push of contacts and calendars) but the iTunes Store and the App Store won't. While the App Store keeps spinning the iTunes Store says "Cannot connect to the iTunes Store". Has anyone else experienced a similar phenomenon?
thanks
Message was edited by: samaki

We're having the same issue. App Store and iTunes do not work when all traffic is tunneled over VPN. Yet, other applications like Safari, New York Times reader, Telnet, etc... work perfectly fine over VPN. If we have the iPhone switch over to using split tunneling VPN mode, then the App Store and iTunes work since they do not appear to be sending traffic over the VPN tunnel. I can say for certain that no outgoing traffic is being blocked on the VPN servers since I administer those servers. I also did a packet capture on the iPhone wireless session and it appears that the App Store sends traffic over the regular HTTP port. So it really doesn't make any sense from a VPN perspective why Safari would work but not the App Store or iTunes when you're tunneling all traffic over VPN. Our iPhones are using the latest firmware (5F136). If anyone has any update, please do share.

Cannot connect to EM on ODD guest from Windows host

Hello,
I cannot connect to the Enterprise Manager in my guest VM from my host. From a IE v8.0 browser, the recommended link https://192.168.56.101:1158/em fails to connect.
I installed Oracle VM VirtualBox 4.0.4 on a Windows 7 laptop and imported the Oracle Developer Days (ODD) VM appliance. Within the ODD VM I started Enterprise Manager with the cmd "emctl start dbconsole". I confirmed the listener is up and running in the ODD VM.
I checked my Windows Firewall and the MS Telnet Client is allowed through on IP 192.168.56.101 on local port 1158.
Suggestions?
Cheers,
David

Apple Support could reproduce the problem, and provided the solution:
Assuming that VNC is configured in the sharing prefs (under Apple Remote Desktop), it is enough to disable ARD in the sharing prefs. Once you do this (presumably via Apple Remote Desktop) you'll obviously lose your connection.
To restart ARD again from the commandline, connect to your server with ssh and issue the following commands:
sudo /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/k ickstart -activate
sudo /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/k ickstart -restart -agent
now you should be able to connect to your server with ARD again....
.... and all connections with VNC should work as well!!
splendid, thanks apple support!

Windows VNC clients cannot connect to Snow Leopard Server native VNC server

I am resurfacing the following related comment made in another post that discusses the same issue I am having with VNC on Snow Leopard. This is still an issue and I cannot connect to our Xserve's Snow Leopard Server with a VNC client on Windows.
I don't want to install another third party VNC server onto our SL Server, and am looking for a VNC client for windows that will connect to our SL Server.
Does anyone have any solutions?
== QUOTED TEXT BELOW ==
Re: Newbie: Connect Windows -> OSX Server
Posted: Nov 4, 2009 9:26 AM in response to: Antonio Rocco
I would politely disagree. Yes, definitely, the Mac 'Screen Sharing' app works a treat, and Apple Remote Desktop.app works as well, but I am coming from a Window's PeeCee.
For me, connecting to my 10.5(.8) Server via tightvnc gives 'Server did not offer supported security type!". Using RealVNC to this machine states "No matching security types Do you wish to reconnect to ... ?" a telnet to this AppleVNCServer service (port 5900), shows RFB 003.889 *, or Remote Frame Buffer Major 3, minor 889.
Also, connecting to multiple 10.6(.1) Clients with Tightvnc correctly asks for a password but then hangs at "Status: Security type requested". Using RealVNC opens, connects, asks for authentication, and exits. Telneting to this AppleVNCServer service (port 5900), also shows RFB 003.889 *.
The Current Version of the protocol is supposed to be 3.8, that is Major version 3, minor version 8. Not 80 or 800 but Eight). http://www.realvnc.com/docs/rfbproto.pdf and I believe that tightvnc only supports up to version 3.7.
On each station I have installed the 'old' OSXVnc.app as a service (to a unique port). OSXVnc utilizes protocol 3.3 and I can control them successfully, but that is of my own doing because of this issue.
Now JollysFastVNC works a treat to any machine I have EVER tried to connect to. I have not tried COTVNC or any of the others (too slow for me, when they wer e around)
Also, I just noticed that RealVNC states that their free and personal version will not connect to Mac OSX (x86 and PPC) but the Enterprise one will. I just Dl'ed the Enterprise Viewer and it gave essentially the same thing ('protocol is not valid' message, even after it asks for a password). Anyway, I am not here to hijack this thread, just trying to keep the info flowing and open.
Maybe I am the only one with these problems but the bottom line is I cannot use Real or Tight, or UltraVNC to administer my server or clients as long as AppleVNCServer gives out the 003.889 protocol version.
Peter
* The ProtocolVersion message consists of 12 bytes interpreted as a string of ASCII characters in the format "RFB xxx.yyy\n" where xxx and yyy are the major and
minor version numbers, padded with zeros.

Searching on the net brought me to the same solution that Mr. Hoffman found as well, I was a bit skeptical at first but since he recommended it, and all my other attempts failed, it was a last resort and I have some additional notes of my own for a successful solution. Read the two links below first before doing anything, as they contribute to the solution in tandem.
http://forums.macrumors.com/showpost.php?p=7221295&postcount=20
http://forums.macrumors.com/showpost.php?p=9081641&postcount=28
I should probably just create an entirely new post with all of the steps that worked for me, but it's rather straightforward nonetheless.

Cannot connect to hyperion financial reporting in EPM 11.1.2.1

Dear all,
I cannot connect to FR in EPM 11.1.2.1 on test server , and this problem avoid us from migrating to production .
I successfully conigured FR and install it on our system . But we still facing the same problem . We already followed some steps published in OTN .
*1- Reconfigured FR and redeploy and reconfigure web server. but nothing changed*
*2- Create new user and provision him to all roles then refresh the security filters but nothing changed*
The test server is 2008 Win OS , 64 bit.
EPM version is 11.1.2.1 .
we received the following 2 errors .
*1- in FR : "You are not authorized to use this functionality. Contact your administrator."*
*2-In workspace : "Required application module reporting.HRImport is not configured"*
Kindly, support.

For the below issues, we had the same issues earlier....
we received the following 2 errors .
1- in FR : "You are not authorized to use this functionality. Contact your administrator."
2-In workspace : "Required application module reporting.HRImport is not configured"
First error will come in different situations....
->If FR studio/BI installed in different server, you are trying to connect from other machine, it will give the error.
For this you need to contact firewall/windows team to open the required ports to be open (ex: 19000/8297,etc), we have asked firewall team to open all hyperion ports from main server to source & vice versa, then it worked.
Note: If BI/FR installed unix, you are trying to access from windows, you need to get all ports to be opened vise versa. please make you are in the same network. try to ping telnet ports from source to destination for each port and vice versa.
->Also the same (1st error) will come if BI services down & not able to ping the FR installed server/work space services. and make sure your admin id should have all admin privilizes.
Second error:
-> Whenever workspace/FR studio services are not up, then will get the error, try to restart directly from /bin folder or try to check the status once you restart (sometimes due to closewait/hung connections), will face issue.
Actuall the same error will come even in 9.3.1 version.
Note: I am just sharing my environment issues and fixes, faced same issues & error and get it resolved with help of windows team. apologize if i am wrong in your envrionment & issue.

Cannot connect to ANIServer7.0

Hi,
I know there is posts about this, but haven't found a solution that works for me.
I having problems with topology view in Cisco Prime LMS 4.1. LMS 4.1 is running as an virtual appliance.
When trying to start it, I get the message:
Cannot connect to ANIServer7.0-CISPRI001
1. Unknown Hostname
2. Unknown Error
Recommended action
1. Check if hostname is DNS resolvable
2. Check whether the ANIServer process is up and running.
I known the hostname is resovable, nslookup gets the ip address from the DNS server.
I know that the ANIServer prosess is running, although it says:
"Running with busy flag set". Not sure why busy flag is set and what impact that causes. But this tread, https://supportforums.cisco.com/message/638316#638316, says not to worry.
I've read these treads:
https://supportforums.cisco.com/message/3434242#3434242
https://supportforums.cisco.com/message/3438511#3438511
Ping hostname works, telnet to the hostname and port 42342 works (but not 43242 which is should work according https://supportforums.cisco.com/message/3438511#3438511, but I'm not sure if thats true)
Clearing the java cache did not help.
The server has been restarted several times, after doing changes that requiers restart.
I'm running Java 1.6.0_24.
Since this is an virtual appliance, and not windows-server, I'm not sure if I can test topology from the server.
What have we done? Well, we removed several devices from LMS to concetrate on our core netwok. Also removed seed devices that we don't need at the momement.
Now I'm not sure what to do.
What now?
Br
Geir

1. Has it ever worked? If yes, has anything changed? If no, then your installation may be suspect.
2. Do you get the same error when you are at the server itself (as opposed to accessing LMS remotely via a browser)? If yes, then the ANIServer process is likely not running. Look here for instructions on how to perform server self test and restart processes.
3. If the problem is limitied to client acess, I'm assuming you've checked suggestion #1 in your post. Beyond that, I have seen a similar issue when Java is not running the exact version (1.6.0_24) recommended by the LMS. I've also seen a clear of the Java cache remedy this issue.
Hope this helps.

Cannot connect to Reverse Proxy

Hi- I have what I think is a basic Lync setup, but it's basica-ally driving me crazy! What I have is:
1 Standard Edition Server
1 Edge Server
1 Reverse Proxy (IIS with ARR)
1 Office Web Apps Server
I've followed some of the numerous how-tos to set up these boxes. My internal setup works great with no issues.
I've worked with my security admin to get the firewall rules set up.. We have SSL certs (with SANs) installed and assigned on RP and Edge. I've set up persistent routes on RP and Edge to FE server. I can telnet from Reverse Proxy to Edge and
back. I've ran netstat to ensure both are listening on 443. But when I run the Microsoft Connectivity Analyzer (online) results show that connection to port 443 on the server failed and says that the port is either blocked or not listening.
Using the Lync Connectivity Analyzer (in house) shows that a connection to "Lyncdiscover.domain.com" failed.
Any insight is greatly appreciated.
Thanx

Public DNS records verified. (Although I do see some posts that say to create CNAME records instead of A records (we created A records) and other posts that say it doesn't matter.
Rewrite rules in IIS ARR verified.
I've triple-checked the certificate (issued by Digicert) and the simple URLs are all listed in the SAN:
sip.domain.com, meet.domain.com, dialin.domain.com, lyncdiscover.domain.com, and officewebapps.domain.com
Here's the error generated by the LCA:
An error occurred while sending the request.
Unable to connect to the remote server
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 [xx.xxx.xxx.xxx]:443
If I try to open the Default Web Site from the server, I'm first presented with "There is a problem with this website's security certificate. The security certificate presented by this website was issued for a different website's address" message.
Clicking on "continue to this website" I get a "403-Forbidden" error. I read in another post that this message was as expected.
Trying to connect to lyncdiscover.domain.com from a browser on the RP returns a "Server not found". [This leads me to believe that the request is not getting through the firewall]. Attempts to access the simple URLs returns a "This page cannot
be displayed"
All services work internally...
More telnet testing: As previously posted, I CAN telnet between RP and Edge (external IPs) but CANNOT telnet to public IP of RP on 443
A similar issue with the Edge Server: netstat shows 0.0.0.0:443 listening but cannot connect via telnet to public IP on 443
RELATED QUESTION: Do I need the SANs included on my internal cert, too?
Thanx
SteveSmo
"Never, ever doubt what nobody is sure about." -Willy Wonka

Failure - Cannot connect to Microsoft SQL Server on localhost

Hi!
I have a sqlserver installation on localhost and I want to connect with sqldeveloper.
I fill connection name, username, password, hostname: localhost port: 1433
and then click on retrieve database.
I get the following error message: "Status: Failure - Cannot connect to Microsoft
SQL Server on localhost"
I don't know the reason. I can use another connection to another ms sql server
and it's no problem, but can't connect to localhost.
I have special signs in my computername, for example a "-". Is this the problem?
How can I solve it?
Thank you
Andreas

I am able to successfully connect to my local SQLEXPRESS instance using the following settings:
Hostname: localhost
Port: 1433/DBName;instance=SQLEXPRESS
Even though I use this to connect, I cannot open a tcp connection to port 1433 via telnet. I believe this goes hand in hand with specifying the instance. As I understand it, there are two ways to specify the port, one is directly, the other is through a named instance (another port is used as a service to look up the correct port). SQL Server 2005 appears to prefer named instances instead of specific ports. When "instance" is specified, the port can actually be any number, the driver apparently ignores it.
The Retrieve database (list) appears to be only for informational purposes. I have to specify the database in the Port field (DBName) regardless of what I have selected in this list.
Hope this helps!
PS: Retrieve database will give that error until instance is specified in my case.
Edited by: flszen on Feb 4, 2009 1:29 PM

Cannot connect to FMS 4 using rtmfp

Hi people,
I was try to connect my FMS 4 development server (Redhat linux OS) in live which was not connected, but the same setup in local windows is connected.
I do know whats the exact problem. Also i will stop the iptables in linux but no use. Please any idea, its worthful.
thanx and regards
Suresh

Hi Nikhil,
Appreciate your reply.
Both Firewall and the SELinux are disabled. But still cannot access the FMS
Server using http://ip-address. Windows installation works perfectly. But
still I can Telnet to port 80,1935 and 111 in the Linux installation. This
is weird. I don't know why the only the Linux setup is not working. Any
idea that I need to change any configuration in the Linux setup? Here is
the Linux version I've installed,
Re: Cannot connect to FMS 4 using rtmfp# uname -a
Linux GSMedia 2.6.18-274.12.1.el5 #1 SMP Tue Nov 8 21:37:35 EST 2011 x86_64
x86_64 x86_64 GNU/Linux
Re: Cannot connect to FMS 4 using rtmfp# cat /proc/version
Linux version 2.6.18-274.12.1.el5 ([email protected])
(gcc version 4.1.2 20080704 (Red Hat 4.1.2-51)) #1 SMP Tue Nov 8 21:37:35
EST 2011
Re: Cannot connect to FMS 4 using rtmfp# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 5.7 (Tikanga)
Thank you.
Viraj
From:     Nikhil Pavan Kalyan <[email protected]>
To:     Kularatnav2012 <[email protected]>
Date:     01/05/2012 03:57 AM
Subject:     Re: Cannot connect to FMS 4 using rtmfp Cannot connect to FMS 4 using rtmfp

6.1 Client cannot connect 6.5 Server?

We have two versions of Essbase Server. One is 6.1 and the other is 6.5. We want to connect both server using only one set of client software. I cannot connect to 6.1 server using 6.5 client software, it said version problem or something like this. When I connect 6.5 Server using 6.1 client software, I cannot connect the server at all, it said tcp/ip problem. I can ping or telnet to the server OS. Is it possible for me to connect both 6.1 and 6.5 server using the same client software?

Generally, client software is "forwards compatible" meaning an older client can usually connect to an older server. The reverse is not true, unless you are on Essbase 6.2 or greater (the Essbase 6.5 API can talk down to a 6.2 server, but not any older).When clients are looking to upgrade, I tell them that - but in the same sentence recommend keeping client software on the same version/patch as the Essbase server. Issues like the one you are having illustrate the types of issues you can encounter - and Hyperion will just tell you to use the proper client version.That aside - one thing to check for - Essbase 6.5 allows a DBA to change the listening port of the server. The default is 1423, which the 6.1 client will try to connect to. Make sure the 6.5 server listening port has not been changed (you have to set up the parameters, so it won't just happen for no reason).Regards,Jade------------------------------------Jade ColeSenior Business Intelligence ConsultantClarity [email protected]

Changed Base Station security; not cannot connect

Added WPA2 Personal security to AirPort base station this morning, now one of three computers cannot connect to the network, despite repeated reboots and connection attempts (Network name and password checked for typos each time).
The machine in question is a PowerPC G4 running OS X (10.4.11).
Any suggestions as to where I start to sort this out?
It's got a lot of vital data on it, but it's in the basement, and running up and down stairs is a strain on aging and arthritic knees.

The Base Station does not have anywhere near the security capabilities of the PIX. It also doesn't cost anywhere near what the PIX does. Where it gets the security it does have (in Base Station mode) is from PAT and its lack of support for static translations. As well, Telnets and HTTP access from the ethernet side (in Base Station mode) are disabled, so those out on the Internet pointing browsers and telnet clients at random addresses are not going to get access. That's why fresh from the box or a reset, administration has to be done from the radio side.

Telnet cannot connect

Similar Messages

Maybe you are looking for