Ivor007

I setup WINS on an NT4 server. I use W2K Pro on my desktop. There is no trust relationship between the domain I have my machine in and the domain where the WINS server resides. I can open the shortcut to the server for Server Manager, User Manager for domains, etc but when I try to connect to the WINS shortcut it tell me "Access is Denied". I am an administrator on the WINS server's domain. I login on my desktop to another domain. However, my username and password for both domains are identical. I can run Server and User Manager through shortcuts. I can launch the WINS admin applet with the name of the server configured as a WINS server but cannot connect. I can open the WINS administrator on the WINS server and from any other machine in the WINS server's domain. Wghat did I over look to overcome this problem? Any answers? Thx Ivor

It gives me the same error message whether I try and run the manager with my local account which is identical to the one in the other domain or if I run the manager running the short cut as the administrator of the other domain.

Yes, they are.

I've tried launching the WINS manager that comes with the ADMINPAK and got the same result "Access is Denied". Also, I can launch the shortcut. I can add the server but it just doesn't connect.

Here's the scenario again, maybe it's a bit clearer. After that I answered your questions: Two domains (A and , no trusts between them. User's account and password is identical in both domains. User's machine in 2000 domain (. Created WINS server in domain A. When user configures shortcut to USer Manager and Server Manager on WINS server in dom A, all work well. When user uses shortcut for WINS admin, message received: Access is Denied. User's account in Dom A has admin rights. The WINS applet launches but cannot connect to the WINS service. Any help apprecited on this one. The WINS service is configured on an NT 4 server. I'm trying to connect to the WINS server from a 2000 domain with W2K Pro as a client. I configured a shortcut from W2K to use: \\<ServerName\Admin$\System32\Winsadmn.exe. This ensures that I use the NT WINS admin and not 2000. It works for Server Manager and USer Manager, why not WINS manager?

The easiest way to check your RPC activity is with Perf Mon. Open a perf mon session for that machine and monitor your individual processes and check which one is using the most resource. Once you've isolated your thread using the most resources, check how many Virtual Bytes the process is trying to use. This would usually be an app trying to do a remote operation. Should the virtual bytes be large, it indicates that that's the amount of resources it's trying to use (Virtual Bytes that is). You have to execute perf mon on the machine as RPC will not allow another connection if it claims to be too busy!

Are your secure channels in place. Use NLTEST.EXE from the Windows Resource Kit and check that the secure channels are operational. Hope this helps.