Welcome, Guest. Please login or register.

Author Topic: telnetd.device ?'s  (Read 4396 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline THEWASPTopic starter

  • Newbie
  • *
  • Join Date: Nov 2003
  • Posts: 41
    • Show all replies
    • http://www.thewaspnestbbs.tzo.com/waspnest.htm
telnetd.device ?'s
« on: January 30, 2004, 06:38:59 AM »
Trying to get my bbs up and running. Amiga 3000 WB2.1    Got amitcp 4.0 going on it and the xsurf running. I can telnet out using the telnet command and I can use an FTP program to get out so I know the card is working on the internet.

Installed telnetd.device   and configured my bbs   put the telnetd.device  in instead of the serial.device and set the appropriate unit #.

When I load the bbs node   I get  telnetd.device error - Couldnt bind name to initial socket (48)

ANy ideas what this could be?


THEWASP
 

Offline THEWASPTopic starter

  • Newbie
  • *
  • Join Date: Nov 2003
  • Posts: 41
    • Show all replies
    • http://www.thewaspnestbbs.tzo.com/waspnest.htm
Re: telnetd.device ?'s
« Reply #1 on: January 30, 2004, 06:58:22 AM »
I know that.........

I am wanting to know what the problem would be!



THEWASP
 

Offline THEWASPTopic starter

  • Newbie
  • *
  • Join Date: Nov 2003
  • Posts: 41
    • Show all replies
    • http://www.thewaspnestbbs.tzo.com/waspnest.htm
Re: telnetd.device ?'s
« Reply #2 on: January 31, 2004, 12:27:30 AM »
Any ideas on what the modem init commands should be for the bbsnode? I think I may have a conflict there. The .conf file is configed right. Miami is working.



THEWASP
 

Offline THEWASPTopic starter

  • Newbie
  • *
  • Join Date: Nov 2003
  • Posts: 41
    • Show all replies
    • http://www.thewaspnestbbs.tzo.com/waspnest.htm
Re: telnetd.device ?'s
« Reply #3 on: January 31, 2004, 08:57:37 PM »
Welp I guess I have finally reached the end of my rope and accept defeat.   No way can I get this Amiga to work via telnet to the bbs.

telser locks the computer up completely upon bbs node boot up. Even the pointer disappears.

telnetd.device using amitcp  will guru the machine when a telnet connect is tried to the bbs.

Using Miami and telnetd.device will allow boot and a connect if tried but the bbs never kicks in. The amiga seems fine otherwise with no lock ups or crashs.


Everyone is telling me its a piece of cake just tell your bbs to use this device instead of the serial.device and away you go.  Its not that easy!


THEWASP
 

Offline THEWASPTopic starter

  • Newbie
  • *
  • Join Date: Nov 2003
  • Posts: 41
    • Show all replies
    • http://www.thewaspnestbbs.tzo.com/waspnest.htm
Re: telnetd.device ?'s
« Reply #4 on: January 31, 2004, 09:11:43 PM »
Quote


Did you set the AmiTCP:db/inetd.conf file?
Quote:
--------------------------------------------------------------------------------


telnet stream tcp dos bin - echo The telnet service is not installed

--------------------------------------------------------------------------------


Where is the "- echo..." you should give the telnetd's path.

I don't know anyway how to set it with telnetd.device, I used the telnetd2 which is not a good idea for a BBS (anybody can have full access on your Amiga).




Yes I did

telnet     stream tcp dos bin sys:devs/telnetd.device


Upon boot of the bbsnode i get a small window that says......telnetd.device error - Couldnt bind name to initial socket (48)

After I click OK the bbs node unloads and gives me the cli back. If I try to load the node again i get a line in the amitcplog    if I try t connect to the node......

Day-time     [err    ]: inetd[7ca39e8]: telnet:  Systemtaglist() failed


Anymore ideas? I feel like its got to be a minor setting I am overlooking or not aware of.

THEWASP
 

Offline THEWASPTopic starter

  • Newbie
  • *
  • Join Date: Nov 2003
  • Posts: 41
    • Show all replies
    • http://www.thewaspnestbbs.tzo.com/waspnest.htm
Re: telnetd.device ?'s
« Reply #5 on: February 04, 2004, 07:42:09 PM »
Quote
Yes I did

telnet stream tcp dos bin sys:devs/telnetd.device

--------------------------------------------------------------------------------


telnetd.device is not an executable binary. I might be wrong (as I said before, I've never set it with telnetd.device), but shouldn't be like that. It needs the demon's (telnetd) binary that makes use of telnetd.device (the device is called by the executable binary), or something like that




I've tried all combo's that I could think of. Some say to take any reference of telnet out of amitcp's startup. I am at a loss! I have a feeling it something stupid I am either doing or not doing.


THEWASP