samba + xp issues

[FUBAR]

Has anyone noticed any oddresults from using samba with WindowsXP for the clients? The specific issue i am seeing is when I try and run an executable off of a share. It seems that sometimes it will work, but most times the first time you try and run some things (mainly setup programs) they will hang explorer for about 30 seconds then come back with an error. I can't remember the exact message but I think it's something with ReadProccess, whatever that means.

I notice this on several different boxes, so it can't be a fluke, but I'm wondering if anyone else has noticed this and maybe seen a fix. I have seen it happen on both Linux servers and Solaris servers, both of which can serve to 98 and 2000 clients properly, but they all have these issues with XP.

Thanks

 

[Heisenberg]

Yeah, I have noticed this, actually. I'll try to run something, and it will lock up the explorer window for the share. I've never seen the error message you describe, but I usually just kill the process, and don't wait. I only have XP running, so I can't test it side-by-side with 98/2k, but I don't remember having that problem before I went over to XP. The machine I have samba on is running FreeBSD 4.6, btw. It's probably a bug in XP if it happens cross-platform like that.

 

[FUBAR]

I was assuming that it was some change that XP made to it's network usage that samba hasn't mirrored yet. I was really hoping there was a registry hack on XP or a parameter that I could try to use on samba to clear it up...

Here's hoping that the samba people will find it and work around someday.

Anyone else?

 

[Gooberlx2]

I'd rather just hope that M$ would someday better implement the concept of networking.