Search results for query: *

Since you have other netware boxesin your tree I would strongly suggest that you ensure the other server(s) have at least one replica of ALL the partitions in your tree (assuming you ahve any partitions). That way if you do an upgrade and loose the server you have not lost the NDS.

Marvin Have had an ongoing saga with Networker and NetWare. I have now got my 1Gb connected hosts backing up at >10 Mb/s so I am hapy with that. I ahve done so uch it is hard to start telling you where to look. I have found that Networker is very DNS dependant, so look at doing reverse lookups...

We have found a solution. It appears there is a bug in the img code (confirmed by Novell as they are reporting this solution to engineering for a rebuild) If you use the command line for img and make sure to use "/" not "\" in the paths. This solves our problem hope this...

Pagey Have you had any developments with this issue? We have the same issue and have conatcted Novell for help but they have not made any progress either. We have noticed that it occurs only on the new Seagate drives shipped by Dell in the GX270's. Any info would be appreciated, If we gwt a fix...

Guys I have had this issue and thought that if name resolution worked then that was all I needed. In fact you need to check the reverse lookups. When the server recieves a data packet from the client it does a reverse lookup on the IP to see if it matches the clients name??? See if the server...

Try a reverse lookup from your networker server to your NetWare client. When the datastream session is being setup the server will reverse lookup the client to ensure it is the client it thinks it is.

Can you change the flag on anonther box running WINNT Client32 v4.83SP1 or are all WINNT Client32 v4.83SP1 doing the same thing? Try using the DOS shell comammnds as opposed to the explorer and see if that works. If so then it might be a client API thing (just on the one system) so back rev the...