Nothing's jumping out at me in the config file, and if your machines are on the intranet together, it's doubtful there's any NAT going on.
Some information I should have asked for the first time: (1) What does fuslogvw.exe show for both the client & server process? Run fuslogvw.exe on both machines (it's on the path from within a 'vs.net command prompt' shell), enable logging of errors, clear the logs if they're not already cleared, then run your test and refresh the view of both logs. Is an assembly resolution failure happening on one side or the other? If so, which process is reporting the failure and what does the log entry look like? (2) If (1) shows an assembly resolution failure, what's the assembly deployment picture look like? IOW, client.exe and somelib.dll are in directory X on machine A, and server.exe and somelib.dll are in directory Y on machine B. Or if they're in the GAC, etc. -Mike DevelopMentor http://staff.develop.com/woodring > > -----Original Message----- > From: Moderated discussion of advanced .NET topics. > [mailto:[EMAIL PROTECTED] On Behalf Of Ned > Sent: Thursday, June 26, 2003 1:51 AM > To: [EMAIL PROTECTED] > > Hey Mike, > > here is the info you asked for:
