[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference noted::windows95

Title:Microsoft Windows 95 ("Chicago")
Notice:Please read topics 1 to 22 before writing anything
Moderator:EEMELI::BACKSTROM
Created:Mon Nov 14 1994
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2958
Total number of notes:19968

182.0. "Trouble mapping network drive?" by NUTS2U::LITTLE (ATG/EOS/Object Infrastructure/me) Wed Dec 21 1994 05:36

T.RTitleUserPersonal
Name
DateLines
182.1I Do Not Know What is Wrong but This is What I Did...DECWET::SHOEMAKERFri Dec 23 1994 05:2515
182.2That did the trickNUTS2U::LITTLEATG/EOS/Object Infrastructure/meFri Dec 23 1994 05:563
182.3Problems when you don't map a drive letter...HYDRA::catherine.crl.dec.com::ALDENKen AldenTue Jan 03 1995 15:239
182.4That's why I needed to map the driveNUTS2U::LITTLEATG/EOS/Object Infrastructure/meWed Jan 04 1995 14:248
182.5How do I do itWMOIS::NILSENFri Mar 07 1997 15:257
        I was told I could use my vax account as a network drive. When I try to
    map the drive, I get errors. I was going to use my network drive letter
    as " N "  The path I gave is was \\nodename\username .  Is this right?
    I am using win95. 

    Thanks  Bob

182.6skylab.zko.dec.com::FISHERGravity: Not just a good idea. It's the law!Fri Mar 07 1997 15:4621
There are a bazillion things that have to be set up right for this to work.

First and foremost, the VMS system (I assume this is what you mean when you say
"VAX account") must be running the Pathworks server (or equivalent).

Secondly, you must have either

1) Pathworks on your Win95 machine

or

2) TCP/IP on your VMS machine, a new enough version of Pathworks to run of TCP/IP,
a WINS server or an LMHOST file set up on your Windows95 machine to make the
mapping between the Lan Manager name (\\node) and the TCPIP name of the VMS
machines, and finally there are a number of things to tweak in your W95 setup (like
NETbios over TCP/IP, I think)

If this doesn't help you get it working, it may at least save you some time (if you
don't have the right stuff on VMS, you can give up now!)

Burns
182.7outpos.lkg.dec.com::EKLOFWaltzing with BearsFri Mar 07 1997 17:3619
Re: .6

	You will need PATHWORKS server (V5.0E is the current version for
OpenVMS) software, or equivalent.

	From there, you'll need a LANMAN account that maps to your VMS account. 
The LANMAN account name needs to be the same as the account name you use to log
into your W95 system.

>Secondly, you must have either

	Actually, you needn't have either PATHWORKS client software, or TCP/IP
on the server, provided the VMS system and the PC are in the same LAN, since
NetBEUI will work.

	Simmilarly, the WINS and LMHOSTS stuff isn't necessary, on a LAN, since
the names will resolve via NetBIOS.

Mark
182.8VMSNET::S_VORESmile - Mickey's Watching!Mon Mar 10 1997 14:068
    also, the system manager needs to have created a share for you pointing
    at your sys$login, usually with the same name as your OpenVMS account
    and preferrably has also created a LAN Manager account with the same
    name as you use to log into Win95...
    
    some of which may have happend automatically when/if they upgraded from
    v4, assuming they used the proper upgrade procedure...
    
182.9skylab.zko.dec.com::FISHERGravity: Not just a good idea. It's the law!Mon Mar 10 1997 15:325
re .7:  I guess I'm behind the times...we don't have the NetBEUI version here.

Thanks for the correction.

Burns