I don t have a good understanding of default accounts when using NETCONFIG. I would like to allow people to list files in a specific directory (DIR NODE::), PHONE me and MAIL me. Does this mean I need to specify default accounts for FAL, MAIL and PHONE? If so, what is the purpose of the Default DECnet account , which is the first of the questions in the sequence below:
Do you want a default DECnet account? [NO]: yes
Do you want default access to the TASK object disabled? [YES]:
Do you want a default account for the MAIL object? [YES]:
Do you want a default account for the FAL object? [NO]: yes
Do you want a default account for the PHONE object? [YES]:
Do you want a default account for the NML object? [YES]:
Regards
Rob
And the link is https://route20.codeplex.com/
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Rob Jarratt Sent: 15 September 2012 08:11 To: hecnet at update.uu.se Subject: [HECnet] Second Alpha Release of User Mode DECnet Router
This second alpha release fixes some bugs and limitations. It has been tested in two DECnet areas and seems to be stable enough for more extensive testing.
Interested in any and all feedback.
Regards
Rob
This second alpha release fixes some bugs and limitations. It has been tested in two DECnet areas and seems to be stable enough for more extensive testing.
Interested in any and all feedback.
Regards
Rob
On 14/09/12 21:29, John H. Reinhardt wrote:
On 9/14/12 3:51 PM, Mark Wickens wrote:
On 14/09/12 20:37, Dennis Boone wrote:
> so I updated the MODPARAMS.DAT, rebooted and ran NETCONFIG.COM, but I'm
> getting errors when attempting to reach out over the ethernet. I know
> the physical network connection is OK because tcpip is working fine.
Wasn't there something about starting DECnet first? Try rebooting again
now that the reconfig is done.
De
Well, I never thought this would fix a VMS issue, but rebooting it solved the problem.
Sorry for wasting your bandwidth ;)
Thanks for the help!!!
Mark.
As Dave says, DECnet needs to change the MAC address on the network interface. If you booted and TCP/IP came up and then you fiddled with and started DECnet, the MAC address was already locked in by TCP And DECnet wasn't able to change it. The rebooting allowed things to happen in the proper order. Technically, you could have stopped TCP and then started DECnet and then re-started TCP and it probably would have worked - unless the sysgen parameters were needed and then only the reboot would have done it.
John H. Reinhardt
Yes, of course that makes total sense. It's been a while since I did anything with DECnet, as I say, all this stuff slowly dribbles out of my brain...
Cheers, Mark.
On Sep 14, 2012, at 4:19 PM, Dave McGuire wrote:
On 09/14/2012 03:37 PM, Dennis Boone wrote:
so I updated the MODPARAMS.DAT, rebooted and ran NETCONFIG.COM, but I'm
getting errors when attempting to reach out over the ethernet. I know
the physical network connection is OK because tcpip is working fine.
Wasn't there something about starting DECnet first? Try rebooting again
now that the reconfig is done.
Starting DECnet changes the MAC address of the interface...could it
have been an ordering dependency there?
-Dave
That's definitely a dependency, unless you have a type of interface that supports multiple MAC addresses. The early ones (UNA and Lance) do not. QNA does, LQA emulates that but doesn't really want to. Tulip and later DEC-designed Ethernet adapters (and the FDDI adapters, for those of you that have one) all support multiple MAC addresses, because it was written into the DEC Ethernet architecture specification as a requirement.
paul
On 9/14/12 3:51 PM, Mark Wickens wrote:
On 14/09/12 20:37, Dennis Boone wrote:
> so I updated the MODPARAMS.DAT, rebooted and ran NETCONFIG.COM, but I'm
> getting errors when attempting to reach out over the ethernet. I know
> the physical network connection is OK because tcpip is working fine.
Wasn't there something about starting DECnet first? Try rebooting again
now that the reconfig is done.
De
Well, I never thought this would fix a VMS issue, but rebooting it solved the problem.
Sorry for wasting your bandwidth ;)
Thanks for the help!!!
Mark.
As Dave says, DECnet needs to change the MAC address on the network interface. If you booted and TCP/IP came up and then you fiddled with and started DECnet, the MAC address was already locked in by TCP And DECnet wasn't able to change it. The rebooting allowed things to happen in the proper order. Technically, you could have stopped TCP and then started DECnet and then re-started TCP and it probably would have worked - unless the sysgen parameters were needed and then only the reboot would have done it.
John H. Reinhardt
On 09/14/2012 03:37 PM, Dennis Boone wrote:
so I updated the MODPARAMS.DAT, rebooted and ran NETCONFIG.COM, but I'm
getting errors when attempting to reach out over the ethernet. I know
the physical network connection is OK because tcpip is working fine.
Wasn't there something about starting DECnet first? Try rebooting again
now that the reconfig is done.
Starting DECnet changes the MAC address of the interface...could it
have been an ordering dependency there?
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
so I updated the MODPARAMS.DAT, rebooted and ran NETCONFIG.COM, but I'm
getting errors when attempting to reach out over the ethernet. I know
the physical network connection is OK because tcpip is working fine.
Cohort in crime points out that you do need to do the autogen dance to
get those modparams changes noticed, and that the lavc stuff may nail up
the interface before decnet gets there, so scssystemid and nodeid
matching may be important here.
De
On 14/09/12 20:37, Dennis Boone wrote:
> so I updated the MODPARAMS.DAT, rebooted and ran NETCONFIG.COM, but I'm
> getting errors when attempting to reach out over the ethernet. I know
> the physical network connection is OK because tcpip is working fine.
Wasn't there something about starting DECnet first? Try rebooting again
now that the reconfig is done.
De
Well, I never thought this would fix a VMS issue, but rebooting it solved the problem.
Sorry for wasting your bandwidth ;)
Thanks for the help!!!
Mark.
so I updated the MODPARAMS.DAT, rebooted and ran NETCONFIG.COM, but I'm
getting errors when attempting to reach out over the ethernet. I know
the physical network connection is OK because tcpip is working fine.
Wasn't there something about starting DECnet first? Try rebooting again
now that the reconfig is done.
De
