Donna opines:

> Get some coffee...then return the results of the following:

Always a good idea, unfortunately I am limited to one cup a day....

> linkcontrol @;status=all
> netcontrol net=<ni_name>;status=all  <---- ni_name is probably lan1
> nettool.net.sys;info="status;tcpstat;tcpg @;quit"
> nettool.net.sys;info="res;di;quit"
>
> we need to know what's going on to know what to tell you.       - d

Ah, but since the HP3000 was working properly with other Windows servers I was thinking it must be something about the "new" Windows 2008 R2 64-bit O/S, which it was, but in a different way than I thought:  It was the original set-up where the firewall was enabled that tripped us up.

Another one of the wonders of the modern IT environment - we didn't install it, but we have to support it....

Jim

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *