Hi,
We do not use DNS or WINS. ASU being a port of Win NT, the set up is similar to a NT domain. It integrates seamlessly with an NT domain. This is the domain I am referring to. As mentioned earlier, we only use TCP/IP protocol with static addressing. I assume Win NT / ASU manages the resolution with any settings needed on the PCs.
It may also be noted that we are currently using ASU (on SVR4) in a NCR cluster set up (from where we are migrating to TruCluster with ASU) and have none of these problems.
Harihar K
*****************************************************************************
ORIGINAL MESSAGE
Hi,
Need a problem resolution urgently.
Have 2-node DS20 cluster running Tru64 with TruCluster5.1. Also installed Advanced Server for Unix (ASU) in multi-instance mode and ASU is installed on both nodes as BDC to our single domain that also has Win NT 4 servers. When accessing the ASU cluster alias from a DOS window of a Win95 PC (using "net view \\clalias", where "clalias" is the cluster alias) after logging on to our domain, it very intermittently gives the following error:
C:\WINDOWS>net view \\clalias
Error 53: The computer name specified in the network path cannot be located
or try again later ,Make sure you are specifying the computer name correctly
when the remote computer is available
Also, on Win98 PCs it seems to work fine after about 10 seconds of logging on to the domain. Due to this, we cannot open the server shares from the "Network Neighborhood" utility at that time. It may be noted that at other times (i.e. when we do not get the above error), we can map its shares using this alias without any problem. For your info, our client PCs are 70/30 using Win95/Win98 and use only TCP/IP protocol with static IP addresses.
Why does this strange problem happen? Need a resolution urgently as our migration process is already delayed. Thanks.
Harihar K
*****************************************************************************
RESPONSES
Are you're PC's, servers etc connected through a switch ?? If so, as the switch connection verification set to "on" ??!!??.
If so, whenever you connect to the switch you get an access delay of approx. 10 secs. Turn off access verification !!
I.e. on a CISCO switch "SET PORTFAST ENABLE"
------------------------------------------------------------------------------------------------------------------------
No definate answers, but somethings to check if you haven't
already. It sounds to me like the servers can't be found by the windows
machines. If it was me I would
a) Check the log files for hopefully something more obvious.
b) Check the network settings of all machines involved
c) I'd go for some sort of resolving problem.
If the machines are using WINS, check they have the same WINS servers.
If not, check that the can all be resolved ok.
Try connecting in via IP address instead of names, if you still
get it, then its not a resolving option.
If that still doesn't work, then I wouldn't be sure, probabyl
check Microsoft's technet for something about Samba connections
------------------------------------------------------------------------------------------------------------------------
Are the names resolved through DNS, or WINS or something? Perhaps a problem with a name server? Just a suggestion.
Received on Thu Jun 14 2001 - 10:44:46 NZST