OK, easy bit first - as far as WINS goes, configure your netserver via ops navigator and put your WINS server in the wins address field, but for the scope ID use the @ symbol - doing this in our network enables all our PC's to quite happily find our netserver as/400s. As for the job dying after 30 seconds, it's hard to track down the joba netserver uses - the best solution to troubleshooting it I have found is to start it from the command line and checking your joblog. ALso, grab the Netserver redbook - it's fantastic and has some great tips on troubleshooting. Dwayne Lindner Senior Analyst - Data Centre Wesfarmers Rural Division 184 Railway Parade, Bassendean WA 6054 Ph: (08) 9273 5365 Mob: 0407 386 693 Email: firstname.lastname@example.org -----Original Message----- From: AIV [mailto:email@example.com] Sent: Monday, 22 January 2001 08:15 To: Midrange-List Subject: AS/400 NetServer Hi, folks, I have a strange problem in one of my customers, recently installed V4R5. Starting AS/400 NetServer starts QZLSSERVER and the four (4) Netbios connections can be seen in NETSTAT *CNN, but this lasts just 30 seconds... After that, message CPIB683 is sent to QSYSOPR with reason code 6 and return code 3204 (I think; sorry, I can't remember the exact figure...). The help for that message only adds some info for reason 6 and return code '16' meaning a duplicate name may be in the network, but no info for other return condes... Where can I find the meaning for the rest of return codes of reason code 6 ? No JobLogs show up; only a final message saying NetServer could not be started... What does the 30 seconds lifetime means? Is it in any way related to the typical 30 seconds other jobs asume for lock-wait on some objects, records, or the like? I can't find any such value (30 secs) in the definition of NetServer properties, nor anywhere else. One more related question, we are using a NT 4.0 as WINS Server. The documentation I found so far mentions that once NetServer is configured and up and running, we should add its name to either the network DNS server, or WINS server or to local LMHOSTS file... As mentioned, we are using WINS on the NT 4.0, but to my knowledge, the WINS Server "gathers" all the information of all PC's in the net as the come up in the network, but we never had to "add manually" each individual PC to any WINS list in the WINS Server... What does exactly mean the phase "we should add the AS/400 NetServer to the WINS Server" ? Could that be the reason for the failure of NetServer starting Netbios connections after the 30 seconds mentioned above? Thanks to all, -- Antonio Fernandez-Vicenti firstname.lastname@example.org +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: email@example.com +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: firstname.lastname@example.org +---
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.