Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
-
Client ORPC bind request on TCP port 135 is reset by server
Hello SWGRAY1, I don't remember the details now (I was pulled off this particular problem to go and fix something else) but somebody identified one of Microsoft's major SRPs (security roll-up patches) which conflicted with SNA. The SRP patched lots of things, including I believe some RPC...- jiffle
- Post #5
- Forum: DCOM / COM
-
Client ORPC bind request on TCP port 135 is reset by server
Hi Chip. No there's no firewall between the client and server in this particular case, they're both on the same switch and subnet. Yes the advanced TCP/IP settings allow port 135 (in fact we removed all port controls as part of our testing, as well as unrestricting DCOM access and launch...- jiffle
- Post #3
- Forum: DCOM / COM
-
Client ORPC bind request on TCP port 135 is reset by server
I've got a client trying to use a remote DCOM object. The client is configured with the object's location via dcomcnfg. When I initiate the request I can see the client connect to TCP/135 on the server, and both complete a TCP/IP handshake. When the client then sends its Bind request to the...- jiffle
- Thread
- Replies: 4
- Forum: DCOM / COM
