× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hello Dare,

You wrote:
>Yes, I have the QZLSxxxxx jobs but can not find the system from windows.

OK.  Are NetServer and the windows box in the same domain or workgroup?
If they are different it becomes difficult to impossible to see NetServer.
OpsNav (or our DSPSMBSVRA command) will show you the current domain name
for NetServer.  You can see the PC domain/workgroup name from the Network
icon in the windoze Control Panel under the identification tab.

Frequently you can find NetServer by using the windoze "Find Computer"
option.  I don't use windoze so I'm doing this from memory.  Bring up the
Find Computer panel (from the Start bar but other places expose it too),
type the NetServer name into the entry box.  The default NetServer name is
the same as your system name with a Q prefix.  Note that if it's a new box
and you changed the system name but didn't change NetServer at the same
time the NetServer name may be Q followed by your serial number.  OpsNav
(or our DSPSMBSVRA command) will show you the current name.  The message
sent by NetServer to QSYSOPR when it starts also shows the name.  Then
let Find Computer go off and search for it.

Once you have located NetServer it usually appears in the Network
Neighbourhood panel although you may have to open the correct
domain/workgroup to find it.

If you are using WINS servers in your SMB network then you may also have
to set the WINS and SCOPE values properly in NetServer before you can see
NetServer.  OpsNav (or our CHGSMBSVRA command) will let you do this.
Either method requires that you end NetServer and restart it in order to
use the new definitions.

Also: you do have Windoze Networking installed on the PC don't you?  And
the PC must be configured for NetBIOS over TCP (TCPBEUI) rather than
native NetBios (NETBEUI).

Also: make sure you are current on PTFs.  NetServer is the buggiest piece
of crap to come out of IBM in a very long time.  If you don't have the
right PTFs it will never work.

Regards,
Simon Coulter.

--------------------------------------------------------------------
   FlyByNight Software         AS/400 Technical Specialists
   http://www.flybynight.com.au/

   Phone: +61 3 9419 0175   Mobile: +61 0411 091 400        /"\
   Fax:   +61 3 9419 0175   mailto: shc@flybynight.com.au   \ /
                                                             X
                 ASCII Ribbon campaign against HTML E-Mail  / \
--------------------------------------------------------------------



As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.