| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 182.1 | I Do Not Know What is Wrong but This is What I Did... | DECWET::SHOEMAKER | | Fri Dec 23 1994 02:25 | 15 |
| 182.2 | That did the trick | NUTS2U::LITTLE | ATG/EOS/Object Infrastructure/me | Fri Dec 23 1994 02:56 | 3 |
| 182.3 | Problems when you don't map a drive letter... | HYDRA::catherine.crl.dec.com::ALDEN | Ken Alden | Tue Jan 03 1995 12:23 | 9 |
| 182.4 | That's why I needed to map the drive | NUTS2U::LITTLE | ATG/EOS/Object Infrastructure/me | Wed Jan 04 1995 11:24 | 8 |
| 182.5 | How do I do it | WMOIS::NILSEN | | Fri Mar 07 1997 12:25 | 7 |
| 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.6 | | skylab.zko.dec.com::FISHER | Gravity: Not just a good idea. It's the law! | Fri Mar 07 1997 12:46 | 21 |
| 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.7 | | outpos.lkg.dec.com::EKLOF | Waltzing with Bears | Fri Mar 07 1997 14:36 | 19 |
| 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.8 | | VMSNET::S_VORE | Smile - Mickey's Watching! | Mon Mar 10 1997 11:06 | 8 |
| 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.9 | | skylab.zko.dec.com::FISHER | Gravity: Not just a good idea. It's the law! | Mon Mar 10 1997 12:32 | 5 |
| re .7: I guess I'm behind the times...we don't have the NetBEUI version here.
Thanks for the correction.
Burns
|