YPXFR Errors

[arobart]

One of my NW4.11 servers is getting the following errors in the product kernel screen:
YPXFR-Error-130: Cannot get master of romulus group.byname. Reason: 8130 NIS map data base is bad
YPXFR-Error-20:host name argument is bad
I searched Novells knowledgebase and found TID#200628. a: doesn't apply since I haven't changed the ip address or hostname. b) doesn't apply since both nisbind and nisserv are both loaded. But in c) it refers to "initialize local nameservers" that is suppose to be found under Perform file operations in the Unicon utility. That is not in my Unicon utility! I do have the option to save database to text files, but when I try to do that, it abends the server. Any ideas?
Thanks
Annette

 

[marvhuffaker]

Are you using NIS?

Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting

http://www.redjuju.com

 

[arobart]

Ok, I've done a ton of reading since I posted my last message so I figured out that my main server is running NIS and all my other servers are clients. I have had one server that for the last month I have not had any errors on, but have not been able to see in network neighborhood, arcserve, no webaccess. Then the one in my last message that with the exception of the error messages runs well, I can see in in all applications and no problem with webaccess. So, anyway...I went ahead and reinitalized the databases on my main server and re-booted it. I couldn't believe it. I can actually see the the lost server in all applications again and in webaccess. But....it did not fix the original errors on the server in the first message.
Whats my next step?

 

[marvhuffaker]

Putting aside the error, are there features, functions, or processes that aren't working?

Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting

http://www.redjuju.com

 

[arobart]

I have got one thing happening at that location that is not happening at any other location and I don't know whether it is related or not. But we use a terminal emulation program to access our unix server and about twice a week I will have a user call that can't log in to the unix server. They get a a winsock connect failed. Connection timed out. Re-booting doesn't help and the unix server can't ping them. The only thing that will reconnect them is when the unix server re-boots after the backup at night. Then they're fine. I don't have any oher branch with that problem.
Annette