Anyone here very familuar with psexec?

My sysadmins just poked me going 'why doesn't this work' -- they're trying to psexec from two domain controllers, onto a client system. One works, one doesn't.

Upon inspection, one is connecting via port 135, the other via port 139 (which is blocked). They don't seem to know why one is going via port 135.

cool tip for the firewall :) for psexec, it use smb protocol to be able to connect, 'file and print' service, as such from memory that service use port 135 to 139

@yagmoth555 yeah, figured it out

was a asymetric routing issue

Due to the way the environment is setup, it has a IP which is expected to be in one data centre, actually residing in another data centre

there was a /16 on the firewall routing it to the 'wrong' one. added specific route for that host and now it works fine :D

I'm just pleased I managed to figure it all out myself without having to refer to my team leader as I normally do.

ahh, cool :), really nice for finding the bug, it was buried really far

yah, was weird as I was looking at firewall logs and it's like 'all is fine here!'