We have a Windows NT 4.0 PDC which is also our main file server. We
also have a Windows 2000 server which is serving RAS.
When users dial up and authenticate using RAS, they all try and connect
to our main file server by putting '\\server' (Don't blame me -- I
didn't name it =)) into their Location bar in Windows Explorer. This is
not an issue, as it is a perfectly valid way of browsing network shares.
Unfortunately majority of the time, these users can either NOT resolve
the name 'server' or they can only see one or two shares on that server.
Today for example, one user rang me while dialled up saying he could
only see the "Data" share when he should have been presented with at
least four shares. He was attempting to access a share called
"Resources."
I told the user to map a drive manually, with "net use Z:
\\server\resources." The map was unsuccessful, as the specified share
could not be seen. Running "Net View" displayed only the "Data" share.
I then instructed the user to do a "Net View \\192.168.0.2," and the
remote user was presented with *ALL* the shares he should have seen. He
then had to map a drive to the IP address of the box, rather than its
NetBIOS name. All I could think was "What a joke."
I've seen this so, so many times, and I find it totally rediculous. To
me, this proves that if I were to write up an OSI Checklist I'd get the
following:
DEAD Application
DEAD-ISH? Presentation
:) Session
:) Transport
:) Network
:) Data Link
:) Physical
if all the rest are working, it *HAS* to be a fault of the Microsoft
Networking model. What else could it be?
--
Adam Smith
Information Technology Officer
SAGE Automation Ltd.
[EMAIL PROTECTED]
http://www.sageautomation.com
Phone: (08) 8276 0703
Fax: (08) 8276 0799
Mobile: 0414 895 273
------
You are subscribed as [email protected]
Archives: http://www.swynk.com/sitesearch/search.asp
To unsubscribe send a blank email to [EMAIL PROTECTED]
