Several suggestions:
The name resolution issues probably aren't the reason for the slowdown; they would cause initial access to a remote machine to be slower, but once a connection is open, windows does not resolve the name again, it caches the address. I'd check them anyway, though, because NT and 2k DO use different name resolution mechanisms by default (DNS for 2k, WINS for NT4)
As for the explorer problem, try disabling Web View if it's on; Web View contains a preview pane that will attempt to display a preview of the currently selected file. Since opening a file from explorer also selects it in the explorer window, the system will attempt to load the file it it's associated app AND generate the preview at the same time, thus slowing access.
Aside from that, there will be a speed difference between using the open dialog and using explorer, since explorer must either load the associated application or communicate with it via DDE to open the file, depending on whether the app supports using DDE to control an existing instance.
For apps that do not support DDE, windows executes a new instance of the application and passes it the filename on the command line; for apps that support DDE and specify this in the registry, Windows checks if the app is loaded; if not it executes it. When the app is running, windows opens a DDE connection and instructs the app to open the file
Since the open dialog for an app is part of the application, the name of the file to openis passed (in-process, quickly) from the dialog to the app, and avoids the (slow) interprocess communication required for DDE and/or the (even slower) creation of a new process.