Telnet & FTP Crash (VaxVMS V5.5-2)

[Joko Subuh Sas]

Dear Alls,

I'm using VaxVMS V5.5-2,
Confused, i can't login (telnet) & FTP to VaxMS. i dunno why.
im check network is work, but if im connect to vaxms use telnet (emolator) and ftp not work, just stuck.

somebody told me, maybe error in hardisk. i don't know how to check log system. or check hardware use command.

Any idea? to resolv this problem.

thanks before for helping me...

[Steven Schweda]

> I'm using VaxVMS V5.5-2,

On which hardware?

> [...] check network is work [...]

How?

What, exactly, does "not work, just stuck"
mean? From what are you trying to Telnet?
What is the command you use? What, exactly,
happens? Are you specifying the VMS system's
name or IP address?

> [...] maybe error in hardisk.

Or maybe the power is off. Can you log into
the VMS system from a directly connected
terminal (instead of some network thing)?

[Joko Subuh Sas]

Vax4000 - VaxVMS V5.5.2

I mean, when i connect to the system and put login informations the system close the connection it say
---
Session Closed (0)

Hit ENTER To Restart Session
---
is there something wrong the with connection? or daemon?
"im using windows to connect/telnet the system"
the same thing happend with ftp connections.
but im check ping IP' the system is reply.
how do i restart network daemon or system?

Thanks

[Steven Schweda]

> Vax4000

That's a start. Probably close enough.

> how do i restart network daemon or system?

It depends. Unless you want to simply cycle
the power and hope for the best, it might
make some sense to log into the VMS system,
and try to see what's happening there.

It might help to know which IP product is
running, as this affects the diagnostic
procedure.

[Joko Subuh Sas]

Sir,

Okay thanks,
so how to do i cycle/reboot the system (how command) and what impact if after reboot system? coz.. before im never reboot.

someone told me after reboot: network, ftp not automatically running. right?

[Dieter Rossbach]

There is a very simple way of rebooting: just switch the box off and on again. In most cases, the system ist set up to do an automatic boot after "power on"

Nevertheless: before you do that, check the console. There should (must) be a simple terminal connected to a serial line adapter. If not, use a PC, hyperterm and a cable. Default setup is 9600bd, 8/n. This is very important to track the system reboot sequence. All errors during startup are looged to that console and if the system is not configured to boot automatically, you have to enter the boot command.

If a console is connected, log on as system manager and type the command:

SHOW SYSTEM

This will give us on information about the running system, including if and what tcpip stack is active on your vms.


When you want to reboot, do a proper shutdown first:

$ @sys$system:shutdown

This procedure comes up with a couple of questions. Use the default answers for all but the "automatic reboot" question. Answer this one with "YES".

The system goes down and restarts automatically. Read the console output!

Dieter

[Jan van den Ende]

Joko,

>>>
I'm using VaxVMS V5.5-2,
<<<
By default, that system would NOT be running TCPIP, but DECnet
>>>
but im check ping IP' the system is reply.
<<<
That seems to imply some IP _IS_ present, and active, on this system.

First question: DID it work the way you try it now?
If not, what DID work? Does that still work?

Rather difficult to wild-guess with so little info.

Proost.

Have one on me.

jpe

[Antoniov.]

Hi Joko,
what about
$ UCX SHOW SERVICE

Also add result about telnet and ftp services
$ UCX SHOW SERVICE TELNET /FULL
$ UCX SHOW SERVICE FTP /FULL

Cheers

Antonio
http://it.openvms.org

[Joko Subuh Sas]

Mr, Antoniov.

i've type your command, i think telnet & FTP has been shutdown. i can't copy the log. but im shoot with my camera (mobile)
bellow the photos.
http://www.flickr.com/photos/66154960@N00/872846679/

http://www.flickr.com/photos/66154960@N00/872846671/

http://www.flickr.com/photos/66154960@N00/872846633/

thanks for advice. i need more advice for this problem. thanks before.

[Wim Van den Wyngaert]

J.,

Very original way to post screen output. But next time take a complete picture (the right part is missing).

FTP and TELNET are both ENABLED. So they should work.

Start with FTP because that's more simple to debug. Check on the system in the login directory of the user you were trying to use. There should be a file *ftp*.log. Check if there is anything in it.

Also check sys$sysdevice:[ucx$ftp]ftpd_startup_H00.log (if that's what I saw in your screenshot).

Also try for telnet :
ucx disable servi telnet
ucx enable servi telnet
(this could reset it, idem FTP)

Wim

[Joko Subuh Sas]

Dear,

Bellow msg Error when type ucx disable services ftp/telnet
im login using "operator" account"
and my Boss told me, this VMS using TCPIP not DecNET

http://www.flickr.com/photos/66154960@N00/875117092/

[Wim Van den Wyngaert]

You need to be logged in as a priv user such as SYSTEM. And do
$ set proc/priv=all
before doing the commands (just to be sure).

Wim

[Jan van den Ende]

Joko,

>>>
No privilege for attempted operation
<<<
says it all.

By default your OPERATOR account does not hold enough "privileges" to execute this commoand.

The quickest (but in my view: dirty) way arounf this is to do
$ SET PROCESS/PRIV=ALL
and try againg.
_IF_ your OPERATOR account has been given the rights to enough privileges, this will work.
Id _NOT_ (as it should) then yoy will need another ( eg SYSTEM ) account.

hth

Proost.

Have one on me.

jpe

[Joko Subuh Sas]

Dear Alls,

I've type command :
SET PROCESS/PRIV=ALL (success)

UCX DISABLE SERVICE TELNET (success)
UCX ENABLE SERVICE TELNET (success)
(but still im can't remote Telnet to VMS)
---------
Session Closed (0)

Hit ENTER To Restart Session
---------

but im type command :
UCX DISABLE SERVICE FTP (unseccessfull)
bellow the screenshoot :

http://www.flickr.com/photos/66154960@N00/875117092/

Thanks.

[Wim Van den Wyngaert]

Joko,

The same problem. No privs. You need to be logged in as SYSTEM and/or do set proc/priv=all.

From the console, can you telnet the node itself ? This would/could indicate that the problem is not VMS related.

Wim