This is a known problem with the windows telnet client since before version 1 (I have no idea why it would have worked for you earlier). You'll either have to use a 3rd party telnet software (I use CRT) or connect from another operating system. I should get this up in the FAQ because this has happened to users many times in the past. -- Serge Knystautas Loki Technologies - Unstoppable Websites http://www.lokitech.com/
[EMAIL PROTECTED] wrote: > Hi Serge, > > well, I need to confess that the problem was of a simple nature ... the > directory of my james installation contained a blank... once I changed the > directory I got it going easily :-) > > Now, I'm facing the next problem with the adminstration console... it > won't accept any login (no 'root', 'root') or whatever I configure it to > be... > > My remotemanager.log looks like this > > 1020593150439 [INFO ] (remotemanager): Access from 127.0.0.1(127.0.0.1) > 1020593155056 [INFO ] (remotemanager): Login failed for ���� root > > Does James have problems with local echos etc. ? Or what could this be ? I > found several similar problems for this on the archive... I tried to > telnet with both > Windows 200 Telnet and Token 2... I tried all telnet configurations there > are, but nothing worked --> there's really the need for a nice webApp for > the Admin console :-) > > Like I said, I got James version 1 set-up in a matter of seconds... but I > still struggle with version 2... > > Help is appreciated :-) -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
