MEVA-Lab's services —
domain FB3-MEVA — file service
For all members of Bochum's University of Applied Sciences the MEVA-Lab does provide the campus-wide file service, featuring:
As a university member you do have the LDAP ID mentioned; or you can get one even as guest professor or student. This ID is the prerequisite for using the file service.
Fitting to this LDAP ID you have to
have a domain FB3-MEVA account of the
same name. See
here for further information —
you might already own one those some 3000 active directory
accounts.
File server access
If you were ever involved in a class using domain FB3-MEVA laboratory workstations and did log in successfully, you saw your file server space as Z: drive. The laboratory workstations log in will connect that automatically.
The command net use will display that connection — and it tells you how to do it on any other computer in the LAN. There you would just enter:
net use Z: /user:FB3-MEVA\sfb3xyz \\Pd337s\fb3stud\sfb3xyz password /PERSISTENT:NO
In that case you might as well use another unused drive letter en lieu de Z: (or omit it). Instead of the exemplary "sfb3xyz" you use (twice) your LDAP ID.
password is, of course, replaced by that of your FB3-MEVA account. Omitting it will call a password dialogue.
Under some circumstances (due to a well known Windows bug) an error message might occur, like:
If that too fails ... read on.
Problems — trouble shooting
You have to know your university LDAP ID (vulgo: e-mail account) and its actual password. This is your key to many internal services. For problems call the DVZ or the students service counter.
We, the MEVA-Lab respectively the domain FB3-MEVA, do know nothing about your non encrypted LDAP password. And we refuse to know. You might check your account information with the Web service "Login - Check" (only within campus; accept server certificate PD328S).
From the workstation (PC) you want to use the file service you have to have (ping) connectivity to the servers
If this happens randomly while other workstation don't have troubles it's usually a network problem too (mostly DNS, DHCP or with DVZ's forwarder). Contact the person responsible for that equipment (Lab's leading professor, DVZ).
In the case multiple workstations reliable connections to the file server fail, it might be server trouble (an extremely rare event by the way). Then do call the MEVA-Lab (Bartsch, Nowak, Weinert) directly.
Should you not yet own a domain FB3-MEVA (active directory) account (and hence of course no file server space), you might do all that your self, see here.
For all members of Bochum's University of Applied Sciences the MEVA-Lab does provide the campus-wide file service, featuring:
- file space on a poweful server (PD337S),
- access to it from every workstation — say PC — within the
university's LAN (intranet),
- authentication with the unique
university LDAP identity
that is something like sfb3xyz, mfb4xyz, dfb1xyz, as used for the @fh-bochum.de respectively @hs-bochum.de e-mail access, FB3 PraktOrg and all other self service functions,
- middle sized file space contingent that will gracefully be magnified on
request for laboratory, thesis or project work,
- nightly backup to another (remote) server
(backup without warranty).
As a university member you do have the LDAP ID mentioned; or you can get one even as guest professor or student. This ID is the prerequisite for using the file service.
Fitting to this LDAP ID you have to
have a domain FB3-MEVA account of the
same name. See
here for further information —
you might already own one those some 3000 active directory
accounts.File server access
If you were ever involved in a class using domain FB3-MEVA laboratory workstations and did log in successfully, you saw your file server space as Z: drive. The laboratory workstations log in will connect that automatically.
The command net use will display that connection — and it tells you how to do it on any other computer in the LAN. There you would just enter:
net use Z: /user:FB3-MEVA\sfb3xyz \\Pd337s\fb3stud\sfb3xyz password /PERSISTENT:NO
In that case you might as well use another unused drive letter en lieu de Z: (or omit it). Instead of the exemplary "sfb3xyz" you use (twice) your LDAP ID.
password is, of course, replaced by that of your FB3-MEVA account. Omitting it will call a password dialogue.
Under some circumstances (due to a well known Windows bug) an error message might occur, like:
- Systemfehler 1219 aufgetreten | System error ....
- Mehrfache Verbindungen zu einem Server oder einer freigegebenen Ressource von demselben Benutzer unter Verwendung mehrerer Benutzernamen sind nicht zulässig. Trennen Sie ..... | Multiple connections to a server or .... disconnect ...
If that too fails ... read on.
Problems — trouble shooting
You have to know your university LDAP ID (vulgo: e-mail account) and its actual password. This is your key to many internal services. For problems call the DVZ or the students service counter.
We, the MEVA-Lab respectively the domain FB3-MEVA, do know nothing about your non encrypted LDAP password. And we refuse to know. You might check your account information with the Web service "Login - Check" (only within campus; accept server certificate PD328S).
From the workstation (PC) you want to use the file service you have to have (ping) connectivity to the servers
- PD323S (pd323s.FB3-MEVA.fh-bochum.de) [193.175.115.3]
- PD322S (pd322s.FB3-MEVA.fh-bochum.de) [193.175.115.4 / 192.168.89.4]
- PD337S (pd337s.FB3-MEVA.fh-bochum.de) [193.175.115.15 /
192.168.89.15]
If this happens randomly while other workstation don't have troubles it's usually a network problem too (mostly DNS, DHCP or with DVZ's forwarder). Contact the person responsible for that equipment (Lab's leading professor, DVZ).
In the case multiple workstations reliable connections to the file server fail, it might be server trouble (an extremely rare event by the way). Then do call the MEVA-Lab (Bartsch, Nowak, Weinert) directly.
Should you not yet own a domain FB3-MEVA (active directory) account (and hence of course no file server space), you might do all that your self, see here.