Today I was a site w/o internet access, but I needed to get Cisco into it to
save time relaying commands and information. I had a dial-up connection out
to my ISP, and then thought about the built-in Telnet server that Windows
2000 Professional has. I made a quick guest account for Cisco, and told
them my dial-up IP, which they could connect to, and then once telnetted
into my workstation, they were able to telnet out my NIC to the routers they
needs to get to. Only catch is that you can only have one session up
through it (enough for us):
Microsoft (R) Windows (TM) Version 5.00 (Build 2195)
Welcome to Microsoft Telnet Service
Telnet Server Build 5.00.99201.1
login: cisco
password: *****
Microsoft Windows Workstation allows only 1 Telnet Client License
Server has closed connection
When they were done, I just disabled the Cisco account. Rather handy now
that I have it. I've run into a lot of troubleshooting where it was a real
pain not to have internet access for Cisco to get in (or I didn't control
the customer's firewall, etc.).
After a successful telnet:
*===============================================================
Welcome to Microsoft Telnet Server.
*===============================================================
C:\>telnet 192.168.45.253
Connecting To 192.168.45.253...
--
Jason Roysdon, CCNP/CCDP, MCSE, CNA, Network+, A+
List email: [EMAIL PROTECTED]
Homepage: http://jason.artoo.net/
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
