But what about the CLIENT? We will use the command prompt window to try to directly attach to the
server and share we are being referred to.
Figure 11: Using cmd window to check direct access to a server and share
As we can see from the above screenshot, the client is not able to get to the referred
server/sharename DIRECTLY. The error received is similar to that returned when we tried to follow the
MS DFS link. All of the symptoms above (the error messages about network path not found, the
ethereal trace showing the NetBIOS server name not found, but the server proven available from at
least one other source) are typically indicative of a name resolution issue.
Let’s take a look at the server again, and see if we can figure out where this server is. We’ll use the
HP-UX utility ‘nslookup’.
# nslookup ceres
Name Server: fwd2.cca.mycompany.net
Address: 55.155.155.55
Trying DNS
Non-authoritative answer:
Name: ceres.alf.mycompany.net
Address: 16.113.9.139
Ok! Now that we have an address for ceres, we can address this problem in several ways.
We could set up a wins server and make sure that everyone is using the same source for name
resolution.
We could set up our clients and servers to use the same DNS source for name resolution.
