![]() ![]() It seems like a simple thing to do, but some administrators don’t and later discover that problems at the command line had nothing to do with the session, but the version of the command line. As a consequence, unless you’re working with that system every day, you’ll want to type Ver and press Enter to see which version of the command prompt you’re using. So, the command prompt you’re accessing is the one on the remote system, with all its attendant resources and limitations. The problem is that you’re working with a remote command prompt, not the local command prompt. The short answer is that you have a fully functional command prompt. I’m thinking now that perhaps I should have discussed this topic in “ Windows Command-Line Administration Instant Reference,” but then there is always the question of the cost to other topics and I had no idea when I wrote that book that Telnet was still so popular with some administrators. My book, “ Administering Windows Server 2008 Server Core,” provides a few ideas on the topic, but not very many. Today’s topic is a natural extension of the topics discussed so far -now that you have an interactive session with a remote system (router, server, or workstation, it doesn’t matter), what can you do with it? The last post, entitled “ Sniffing Telnet Using Wireshark,” covered Telnet security issues. I discussed basic Telnet connectivity in the Using Telnet to Perform Tasks post. So far, I haven’t received any requests for Telnet scripting topics, so I’ve decided that perhaps there isn’t a lot of interest in this topic. Today marks the last post in my Telnet series unless someone writes with additional ideas on issues they’d like me to cover. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |