Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
dpc2100r2 its opereational problems
#11
Change comp sys description, nic mac and a different test nonvol. That nonvol is toast on your node now. Unless someone gets really soft hearted and walks you through the telnet procedures to fix it...Easier to just start fresh.
Reply
#12
dear sir i am very thankful to you for your kind information but sir i have an problem because i connect to my eternet cable only but sir please tell me that there is cable feed also connected or disconnected for all these telnet procedure because i apply without cable feed and run putty but there is nothing happening putty works and scan please tell me about cable feed that its connected or not for all this procedure thanks
Reply
#13
how to log telnet
Code:
Method 2) Using ethernet

Remove power from the modem.

Set manual NIC IP 192.168.100.10.

Open Putty. Click the 'session' section of the settings panel:

Connection type: Telnet
Host Name: 192.168.100.1
Port: 23
Close window on exit: Never

Power up the modem. Wait 15 seconds, then click 'open' in putty.
Enter username and password, press enter.

Ignore any crap coming up in the window, it may look like you can't type but you can. May help if you just don't look at the screen

Type this, pressing enter at the end of each line:

cd doc
up_dis

cd /
cd n/b
auto_console 1
write

Note: The lines above are correct for modems based on the BCM3349 (A250/A255/A256/SB5101/Webstar 2100). If you're using a BCM3348 modem (A200/SB5100) the line 'cd n/b' changes to 'cd n/c'.

This tells the modem to halt at the console. Close putty and reboot modem using power cable.

When you reboot it, it won't try to connect at first, so you have time to set putty to log all console output to txt before connecting.


Open Putty. Click the logging section of the settings panel. Select the following options:

Session logging: All session output
Click 'browse' and browse to your desktop folder.
Filename: putty.txt
'Always overwrite it'
Untick 'flush log file frequently'

Click back onto the 'session' section of the settings panel:

Connection type: Telnet
Host Name: 192.168.100.1
Port: 23
Close window on exit: Never


Click 'open', enter username and password and press enter. Type 'run' and press enter. The modem will try to connect.

Wait for about 20s after the connection has reached the failure point, then close putty and it'll save the txt log as putty.txt on your desktop.

Once you've finished you'll need to set auto_console back to 0 in telnet, or you'll have to type 'run' every time you reboot modem.
__________________________________________________________________________________
******new discord chat linkĀ https://discord.gg/5BQQbsb*******
Reply
#14

.txt   putty.txt (Size: 19.66 KB / Downloads: 53) dear sir, here its my telnet post log detail
Reply
#15
it still looks like a signal issue to me plug it directly into the tap and try it then
__________________________________________________________________________________
******new discord chat linkĀ https://discord.gg/5BQQbsb*******
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)