Error message on XP W/Stn during Async Remote 1

[MrP37]

I have one laptop running XP Professional Version 2002. During the Groupwise remote link it opens several boxes all with the same message:
"The master system could not match your domain or post office names. Please correct these in 'Remote Options'."
However, the names are correct and closing the boxes allows the remainder of the connection to go through ok.
Any suggestions?

 

[TheLad]

Try this TID???

http://support.novell.com/cgi-bin/search/searchtid.cgi?/10016272.htm

-----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[MrP37]

Cheers THELAD,
but I've already checked those settings. The thing is that Remote works fine on 98, ME and W2K machines, connecting to the same modem and port on the server. The problem only seems to be on the XP machine.
Any further suggestions?
Thanks Again.

 

[TheLad]

Ok, what version of the Novell Client are you running? The latest is v4.83 SP1.

Also, is your IP configuration on the laptop working correctly i.e. is DNS names being resolved etc... -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[MrP37]

TheLad,
I'm running client 4.83 and I'll check the DNS etc after Christmas when he brings the lap top back.
Cheers for the assistance and have a good Christmas.

Steve

 

[MrP37]

TheLad,
Used the IP address instead of DNS in the ASYNC config and installed 4.83Sp1 as opposed to the 4.83 I was using. Unfortunately, don't ask me why, the new client managed to completely muck up his profiles on his laptop and now I cannot get the laptop to connect at all to our NT server. So its back to the drawing board with his laptop.
I wish our manager had purchased a laptop with W2k on instead!

 

[TheLad]

When you installed the client, what options did you select to install? -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[MrP37]

TheLad,
NDPS printing and Remote Management!
The last thing I remember before it all went very stressful was "Application Launcher Has Been Updated, Reboot."
Needless to say I will now only choose the default options.
I've since dropped the client back to 4.83, and he's able to use it without actually having to be connected to our NT server, it only requires that connection for the virus updates.
When I manage to get the laptop off him again, I'll sort out the connection problem. It's quite amazing how much you can learn about an OS in a short period of time when its the CEO's, and that's true, damn true!

 

[TheLad]

Sounds like it may have installed Workstation Manager during the Client Installation. If that is the case, this will be the reason the profile stuffed up as it was applying settings from a policy on the network.

Funny people, CEO's! Don't want to spend any cash but want everything like now! -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[MrP37]

Your probably right.
We've since installed 4.83SP1 with just the default ticked and had no problems whatsoever.
Ah well, we live and learn!

Cheers Again.

(Can't remember the original problem now).