OK, I'll try to make it a bit more specific than previous answers:
1. I assume that you have a domain user account which could look like "MYDOMAIN\user" (otherwise, you won't be able to access domain resources anyway).
2. Make your computer a member of a WORKGROUP with the same name as the domain you want to be able to access (in our case "MYDOMAIN"). Note, that this is not absolutely necessary, but otherwise you will get problems with browsing the network.
3. You don't have to match you LOCAL logon credentials (ID and password) with those in the domain, but doing so might make it a bit easier for you.
4. Now the most important part -- you WILL have to get a authentication from the domain to access any resources in it. The easiest way to get around this inconvenience and eliminate that login dialog from popping up, is to set up a persistent drive (or printer port) mapping. In the "Map Network Drive" dialog there is an option "Connect as Another User" -- make sure you clickit and then specify you DOMAIN user ID and the password (user ID must be in the form "MYDOMAIN\user"). Make sure that "Reconnect at Logon" option for the mapping is checked. This way, every time you log in locally, you domain credentials will be automatically supplied to domain controller, so you don't have to worry about those annoying logon dialogs. You can also do mapping for drive or printer port from command line using "net use" command with "/persistent:yes" option.
One thing to keep in mind -- this works on "per domain" basis, so, if you have several domains with trust relationships, you have to get an authentication for each trusting domain you are trying to access.
I am using this scenario for myself for a long time, and it works perfectly fine. Any additional questions -- drop me a line.
Hope this helps.