Question : NW6.0 Server changed name mysteriously

Can someone help me change the name (and workgroup if applicable) back. It was "APPLE" and appeared under the "NGS" workgroup. Now showing up as "APPLE_W" under the "WORKGROUP" workgroup. I have not changed a thing and it is causing SAV problems and some minor inconviences. Thanks.

btw... it's NW6 SP5

Answer : NW6.0 Server changed name mysteriously

Honestly, I really don't think it's a problem with the NetWare server, or ever was.  What you went through with PsiCop and I today just did some cleanup and slight adjustments that should be done anyway.

I seriously believe it to be a Symantec issue, or a Windoze issue, and believe you should concentrate on getting that PC and software to recognize/see what it used to before whatever update was done that "broke" it.

Since you don't use DNS, it's not an IP name resolution issue.  It's more likely an IPX resolution issue because Symantec is one of those idjit companies that think the only way to talk to NetWare is IPX, but it could be a NetBIOS name resolution thing, since Symantec is so far up Bill G's butt they see through his nostrils.

As such, it doesn't matter how much you attempt to ping (real ping, that is,) it won't resolve the name.  Without DNS, you can't do NSLOOKUP either.  You could try some Windows-specific NetBIOS-type commands, which I don't remember offhand so I can't tell you exactly what NET command to use.

You need to 1) find out how SAV does its name resolution and then 2) determine what changed on that PC that's affecting how it "sees" the name of the NetWare server.  It's not unusual, sad to say, for a SAV update to break stuff, and it's like pulling teeth to get any satisfaction from Symantec tech support.  First, you have to convince them that it's their problem.  They are among THE worst at pointing fingers and playing the blame game.