- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: ADMIN SEND over PATHWORKS
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-17-2010 07:30 AM
тАО08-17-2010 07:30 AM
ADMIN SEND over PATHWORKS
I have an Alpha DS20E running Advanced Server 7.3B on VMS 8.3
I am trying to run the following command:-
$ DAVE:SYSTEM> admin send
_computer name(s): sandisor
_message: test
%PWRK-E-ERRSENMSG, error sending message for computer "SANDISOR"
-LM-E-NERR_NAMENOTFOU, the message alias could not be found on the network
We have a 2nd Alpha on the same network running VMS7.3-2 and Pathworks 6.0C
the admin send works as this
$ admin send
_computer name(s): sandisor
_message: test
Any ideas what to check?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-17-2010 07:37 AM
тАО08-17-2010 07:37 AM
Re: ADMIN SEND over PATHWORKS
Paul Nunez on anothe thread suggested these checks:-
The way the ADMIN SEND command works is it attempts to resolve the NetBIOS name SANDISOR\0x03 to get the IP address of the system to which the message should be sent.
A similar test would be:
$ @sys$startup:pwrk$define_commands
$ nbshow knbstatus sandisor 03
from upgraded box we get:-
$ DAVE:SYSTEM> @sys$startup:pwrk$define_commands
$ DAVE:SYSTEM> nbshow knbstatus sandisor 03
: No response for sandisor
$ DAVE:SYSTEM>
If you don't get a response it could be because the name SANDISOR\0x03 is not registered on the network, most likely because the Messenger service is not running on the Windows client.
.
The messenger sefvice is running on the client PC
From the client on which you expect to receive the message, do:
nbtstat -n
to see the list of NetBIOS names it has registered. Is there an entry for SANDISOR <03>?
NetBIOS Local Name Table
Name Type Status
---------------------------------------------
E8262ZD50187488<00> UNIQUE Registered
HBEU <00> GROUP Registered
E8262ZD50187488<20> UNIQUE Registered
E8262ZD50187488<03> UNIQUE Registered
E8262ZD50187488<52> UNIQUE Registered
SANDISOR <03> UNIQUE Registered
E8262ZD50187488<01> UNIQUE Registered
xRober├В┬ж.....5a├Г
If the name has been registered, is that client on the same IP subnet as the Advanced Server?
IP addresses of ALphas are
129.94.185.45 and
129.94.185.46
If not, is WINS being used? If yes, it could be a WINS issue too (i.e., the client is using one WINs server while Advanced Server uses another and the 2 WINS servers aren't replicating).
WINS not being used on either server
HTH,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-18-2010 03:52 AM
тАО08-18-2010 03:52 AM
Re: ADMIN SEND over PATHWORKS
If WINS is not being used on either server, then how is name resolution being performed? I suspect your V6.0C server is either using LMHOSTS file or DNS. Do ADMIN/CONFIG, choose Transports and compare your 6.0C server with the 7.3B server. Anything different?
You could try to use DEBUG in ADMIN to see if it gives you any clues. I doubt it will, I think ADMIN just does a "NetMessageSend" or something like that to the APISHR and lets the shareable do all the work. But give it a try on both the 6.0C and 7.3B servers and compare.
$ ADMIN
DOMAIN\\SERVER> DEBUG LOG /EVENT=(APIDATA,INFO,CMDSTATUS)/FILE=FOO.BAR
DOMAIN\\SERVER> EXIT
$ TYPE FOO.BAR
(do ADMIN DEBUG HELP to learn more about ADMIN's debug capability, especially if the above commands aren't working)
Brad McCusker
Software Concepts International
www.sciinc.com
Software Concepts International
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-18-2010 07:51 AM
тАО08-18-2010 07:51 AM
Re: ADMIN SEND over PATHWORKS
the same subnet yes
running the admin/config - both same LMHOSTS and using TCPIP
output from admin commands:-
$ DAVE:SYSTEM> admin
BERTDOMAIN\\DAVE> debug log/event=(apidata,info,cmdstatus)/file=foo.bar
%PWRK-I-LOGOPENED, log file SYS$SYSROOT:[SYSMGR]FOO.BAR;1 opened
BERTDOMAIN\\DAVE> net send sandisor test
%PWRK-E-ERRSENMSG, error sending message for computer "SANDISOR"
-LM-E-NERR_NAMENOTFOU, the message alias could not be found on the network
BERTDOMAIN\\DAVE> exit
%PWRK-I-LOGCLOSED, log file SYS$SYSROOT:[SYSMGR]FOO.BAR;1 closed
$ DAVE:SYSTEM> type foo.bar
16:35:11 ML_LOG+180\ML_Log_OpenLog() Log file SYS$SYSROOT:[SYSMGR]FOO.BAR;1 init
ialized at 18-AUG-2010 16:35:11
16:35:11 MAN_DEBUG+530\Cmd_Debug_Log() Logging events mask = 0x1CA
16:35:11 ML_CLI+297\Cli_ParseCommand() Command completion status is: %SYSTEM-S-N
ORMAL, normal successful completion
16:35:25 MAN_NET+5752\CmdTransDispatch() Calling Cli_ParseCommand
16:35:25 ML_COMPUTER+2278\ML_Comp_GetServerInfo1() NetServerGetInfo(Server="\\DA
VE", Level=1)
16:35:25 ML_COMPUTER+2283\ML_Comp_GetServerInfo1() (S) ApiStatus=0 : %LM-S-NER
R_SUCCESS, normal successful completion
16:35:25 ML_ADMIN+1806\GetServerInfo() ServerName="DAVE" => "DAVE"
16:35:25 ML_ADMIN+1819\GetServerInfo() Local ADMIN user name is "Administrator"
16:35:25 ML_ADMIN+1229\SetAdminInfo() Temporary Administration Information:
16:35:25 ML_ADMIN+1229\SetAdminInfo() Domain="BERTDOMAIN"
16:35:25 ML_ADMIN+1229\SetAdminInfo() Server="DAVE", Alias="DAVE", Domain="BER
TDOMAIN", Version=4.0, Flags: VMS PDC PWRK
16:35:25 ML_ADMIN+1229\SetAdminInfo() Do priv checks: NO
16:35:25 ML_SEND+383\ML_Send_Msg() NetMessageBufferSend(Server="\\DAVE", Compute
r="SANDISOR")
16:35:29 ML_SEND+392\ML_Send_Msg() (F) ApiStatus=2273 : %LM-E-NERR_NAMENOTFOU,
the message alias could not be found on the network
16:35:29 ML_CLI+297\Cli_ParseCommand() Command completion status is: %PWRK-E-ERR
SENMSG, error sending message for computer "!AZ"
16:35:29 ML_CLI+297\Cli_ParseCommand() Command completion status is: %PWRK-E-ERR
SENMSG, error sending message for computer "!AZ"
16:35:35 ML_LOG+222\ML_Log_CloseLog() Log file SYS$SYSROOT:[SYSMGR]FOO.BAR;1 clo
sed at 18-AUG-2010 16:35:35
$ DAVE:SYSTEM>
any further ideas?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-18-2010 07:55 AM
тАО08-18-2010 07:55 AM
Re: ADMIN SEND over PATHWORKS
working server - 255.255.255.128
not working server:- 255.255.255.0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-18-2010 07:58 AM
тАО08-18-2010 07:58 AM
Re: ADMIN SEND over PATHWORKS
And, you checked the LMHOSTS file on both systems and the entry for sandisor is the same?
Software Concepts International
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-18-2010 08:03 AM
тАО08-18-2010 08:03 AM
Re: ADMIN SEND over PATHWORKS
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-18-2010 08:16 AM
тАО08-18-2010 08:16 AM
Re: ADMIN SEND over PATHWORKS
Try changing the mask to match, if you can do so easily - that sort of thing is not my area of expertise.
Next step in my mind would be wireshark to take a look at what's happening on the wire.
Software Concepts International
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-18-2010 08:20 AM
тАО08-18-2010 08:20 AM
Re: ADMIN SEND over PATHWORKS
what is wireshack?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-18-2010 08:28 AM
тАО08-18-2010 08:28 AM
Re: ADMIN SEND over PATHWORKS
but this is definitely not the way it was working on the main server
we have 10 users here with PC's so I could simply add them all to the hosts file i suppose