>>>I have an app I am moving from a 98 desktop to an NT server (4.0 SP4). The following code is in the init method of a custom class used in the app:
>>>
>>>This.oFSO = createobject("Scripting.FileSystemObject")
>>>This.oNSO = createobject("wscript.network")
>>>
>>>In another method used to map a drive before copying files, I issue the following code:
>>>
>>>This.oNSO.MapNetworkDrive(tcDrive, tcUNC, .F., tcUser, tcPwd)
>>>
>>>which maps the drive using the drive, unc, user, and pwd information stored in meta tables (the .f. turns off the UI). This works fine on 95 and 98, as long as the wshom.ocx and scrrun.dll are properly registered. On NT server, the MapNetworkDrive call fails. We manually mapped a drive based on the exact same information used in the method call and the drive map worked as expected. Any ideas?
>>>
>>>My SWAG is that I need updated versions for the ocx/dll files for NT.
>>
>>Forgot to mention, we don't get an OLE exception, it just doesn't map the drive.
>
>did you ever get a command for mapping in NT?
>
>I suddenly have to do this.
>
>__Stephen

Yes we did. I *think* the problem was with the Novell Client configuration. We were able to get the code above to work properly though without any changes. A couple of gotchas you might experience (without knowing the details on what you are attempting). Our environment was the following:

Application running on NT 4 Server SP 5.
Running Novel client for netware connectivity (wanted to use Gateway services, but we have 2 trees to authenticate to and gateway services only allows 1 tree to be configured).

Gotchas:
NT Server doesn't play well with Novel client. The NT gurus here had to play with it for a while (2 gurus, both MCSE and they know their stuff).

I was doing remote admin on the box via PCA and PCA misbehaves quite a bit with the Novel client installed. Ended up switching to VNC for remote admin which does exist quite well with the combination.

We've been playing with running the application as an NT service. It's an automation piece that connects into remote Novel servers spread around the world. The scripting components will work in an app running as an NT service, but there isn't anything for Authenticating to a Novel server. Therefore we have given up on implementing this as an NT service, scripting only works (from everything I can tell) IF you are authenticated already.

If you have any questions on implementation, let me know. Might be able to save you some time.