You can browse down and view the details of the file just like we did in the task manager section above.
Or you can right-click, choose Properties, and then take a look at the Image tab to see the full pathname that is being launched, and you can even see the Parent process, which in this case is the Windows shell (explorer.exe), indicating that it was likely launched from a shortcut or startup item. Now when you hover over the rundll32.exe in the list, you’ll see a tooltip with the details of what it actually is: Simply launch Process Explorer, and you’ll want to choose File \ Show Details for All Processes to make sure that you’re seeing everything. Instead of using Task Manager, we can use the freeware Process Explorer utility from Microsoft to figure out what is going on, which has the benefit of working in every version of Windows and being the best choice for any troubleshooting job. Research Using Process Explorer on Windows 10, 8, 7, Vista, etc If you think you have a problem, you should always run a scan to be sure, but we can verify exactly what is going on… so keep reading. Note: the valid process is normally located at \Windows\System32\rundll32.exe, but sometimes spyware uses the same filename and runs from a different directory in order to disguise itself. This executable is a valid part of Windows, and normally shouldn’t be a threat. Since there’s no way to directly launch a DLL file, the rundll32.exe application is simply used to launch functionality stored in shared. Is this all overly complex and there's an easy way to do what I'm trying to accomplish? Or am I missing some ultra-obvious step that would make everything behave as desired? Most of the stuff that's coming up when I try to Google seems to be along the lines of "My ASP.NET application isn't working!", which obviously isn't all that much use.If you’ve been around Windows for any amount of time, you’ve seen the zillions of *.dll (Dynamic Link Library) files in every application folder, which are used to store common pieces of application logic that can be accessed from multiple applications. Go back to the second client, create a new passkey for the second login, try logging in again.
Go back to the server, create a second Windows account, give it SQL Server rights.Assume that this translates to "You can't have two connections from the same account" (Yes, I know that doesn't make sense, but I'm a bit like that).The login is from an untrusted domain and cannot be used with Windows authentication" Attempt to access SQL Server 2008 using Windows authentication.Start on the second client (Windows 7, SQL Server 2008): Attempt to access SQL Server 2005 using Windows authentication.