Failed creating socket in teamsite 6.7.1

Hello,

I am trying to deploy some page and I get to see the message "Exceeded all 3 retries to get a connection with the target OpenDeploy host.Failed creating socket."

I tried to communicate to receiver via telnet too,but it showed failed to connect.

Also tried the given solutions in other post. But nothing worked. Kindly suggest.

Regards,
Rahul Jain

Find more posts tagged with

Comments

Rohan_t1

There are lot of posts on the devet for this issue. Problem could be with the firewall, OD rcvr down among others. Did you try to telnet 20014? Did deployments ever work there?

jainrahul

Thanks Rohan for reply.

Yes I tried telnet 20014. Also as of firewall, there is no firewall installed which might create a problem on the base or receiver.

Recently I issued the license of teamsite and post iwreset, I am facing deployment problem.

nipper

It is quite simple, this is not an OpenDeploy problem.

Either OD is not running on the receiver, the port is blocked or you have the wrong host name.

Get your networking guys involved. I have seen times where the port was open in one direction but not for the return packet.

ISCBorisB

Two processes (OD Base and OD Receiver) failed to communicate, it is that simple.
It is the issue of your Environment. Few most common reasons (and things to check) for such behavior are, in this order:

1. Receiver is not running.
2. Receiver is "invisible" to the Base. (wrong IP, wrong DNS Name, Firewall blocking traffic in either direction and whatnot)
3. Receiver listens on the "wrong" port (default is 20014)
4. Receiver binds to unexpected IP (may happen when receivers are installed on machines with multiple NICs and/or have multiple IP addresses)

Check these conditions one by one. Get to the next one only after you make sure the previous one is not the case.
Chances are, you'll find the problem along the way...

jainrahul

Thanks for quick thoughts.

I changed the local node name and instead gave the IP address on both odbase and odrcvr. Probably the name initially was unidentifiable.

Now the deployment is happening.

Thanks again.

Adam Stoller

Sounds like a multi-NIC / DNS issue (as previously suggested)
You can usually verify that by 'ping'ing the hostname that you used both on the sender and receiver to verify that they come back with same IP value.