Do you have SLP up and configured propely?
If you do a slpinfo /all does it see all the resources on the network?
Main Topics
Browse All TopicsHi there all, and thanks for taking your time to have a look at an issue im having
on this network we are using, we have 2 OES Servers both at different residenial place connected via VPN Routers
address of the Servers:
OPSERV 10.0.0.3
MADSERV 192.168.200.2
both servers can ping each other
with this login script, im trying to map a drive from both servers
MAP ROOT G:=%FILE_SERVER\SYS:\OSBOR
MAP ROOT Z:=\\MADSERV\SYS:\MADDINGT
any help would be appreciated
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Uhm.
If you're using the Novell client32 for your platform, you should not use the UNC path or an IP address path in your map commands.
In an eDirectory-based environment like this, the recommended method is to use the volume object in the map command.
Say, for sake of discussion, your OPSERV is in the FOO tree, in the BAR org, in the OP OU, and the MADSERV is in the FOO tree, in the BAR org in the MAD OU, and you're actually using "BEST PRACTICES" and DO NOT HAVE USER DATA ON SYS:!!!, and you've called your user data volumes DATA on both servers, then the MAP commands would be:
MAP ROOT G:=.OPSERV_DATA.OP.BAR:\OS
MAP ROOT Z:=.MADSERV_DATA.MAD.BAR:\
HOWEver, the problem MAY be that you're trying to map Z:, which generally is the first search mapping that's done using a MAP INS S1 command, so if there's such a command in your login script ahead of the commands you're attempting, it means Z: is already taken, and you need to pick a different letter.
Regardless, you should use the object in your MAP commands.
Oh, also, if you want G: always to be mapped to the server you log into, you don't need to do it the way you did. just use the volume name - it'll take that volume from the login server and map it.
ex: MAP ROOT G:=DATA:\OSBORNEPARK
Of course, that's assuming there's an OSBORNEPARK directory on all servers, and you're following best-practices and NOT putting USER DATA on ANY SYS: VOLUME, EVER!
Hi there ShineOn, thanks for the advice, not sure i totally understand it thou, but would like to :)
here is a pic of the tree we have currently
http://www.webber4.com.au/
if this can help in my solution that be great, if i need to re-arrange some things to get in the line of 'best practices' that be cool also :)
Thanks for the points.
Looking at your tree pic, I see an inherent problem, design-wise. Looks like someone did it "on the fly" without any training, no insult intended.
When you have multiple locations, you should design the tree for the WAN, with multiple partitions of NDS/eDirectory, to minimize tree-walking across the WAN for authentication.
You should take a look at the documentation at http://support.novell.com/
The fact that you're mapping user data on SYS: also is an indicator that someone set it up without knowing Best Practices. You should have a separate NSS pool for user data volumes, and SYS: should only have NetWare OS files and system files, no user data or even print spool space/print queues. If a rogue user application fills up your SYS: volume, you can not only crash the server, you run the risk of corrupting eDirectory.
It's kinda like designing a Linux server to have only one partition, or a Windoze server with everything on C:. Neither are recommended.
Business Accounts
Answer for Membership
by: alextoftPosted on 2006-04-27 at 23:54:52ID: 16559794
The servers can ping each other, but can the client from whom you're trying to map the drive also ping both of them? Try mapping the drive to \\IPADDRESS\VOLUME\DIRECTO RY then if the connectivity is definitely there we can start looking at issues like DNS etc