I have a website uses enterprise library to log using MSMQ trace listener. Site is creating logs. The logs are in MSMQ outgoing queues. However, queues are not being sent to remote computer. Message I get is
Failed to connect Winsock socket. Address:IP=xx.xx.xx.xx
State is in "Waiting to Connect". The queue path I have as queuePath="FormatName:DIRECT=OS:computername\Private$\private queuename"
Am I missing anything? May be firewall rule? when I look at the firewall rule in destination computer, it allows the MSMQ Inbound TCP/UDP for all ports.
Enabling Remote Event Monitor (RPC-EPMAP) inbound rule in firewall fixed the issue I was getting. Now the state is Connected and Connection History is Connection is ready to transfer messages.
Also to add I found that port 1801 which msmq port for allowing incoming traffic need to be opened.
https://support.microsoft.com/en-us/help/183293/how-to-configure-a-firewall-for-msmq-access
Related
I am working on a product which uses ZeroMQ (version 4.0.1).
The server and client communicate based on ZeroMQ ROUTER-socket.
To read socket events, server and client also create socket-monitor sockets (PAIR). There are three ports on which server binds and listens. Out of these three ports, one port is in a non-secured mode. Other two ports are using md5-authentication.
The issue I am facing is that, both the server and the client spontaneously receive socket disconnect for one of the secure port sockets (please see a log below). I have checked multiple times that server and client both have L3 reachability to each other.
What else I should check for?
What really triggers this error scenario?
zmq_print_callback:ZmQ: int zmq::stream_engine_t::read(void*, size_t):923
Stream engine recv():
TCP socket (187) to unknown:0 was disconnected
with error 107 [Transport endpoint is not connected]
Below sequence of events can trigger this error on server
Server receives ACCEPTED event for clientY and gets FD1.
Link-flap/network issue happens and clientY disconnects but server does not receive this disconnect.
Network recovers and clientY connects back to server.
Server receives ACCEPTED event for clientY and gets FD2. However, packets sent to this sockets does not go out of the server.
After 1 min or so, clientY receives "Transport endpoint is not connected error" for FD1.
Application can use this to treat as client disconnect.
I am having issues with SMTP from one of my web servers. I've verified firewall connectivity over port25 to the SMTP relay and the exchange servers is good to go. I can hit the SMTP relays and exchange server from my web server via telnet. Whenever I drop a mail in Pickup it sits in the queue.
In Event Viewer I get:
Message delivery to the host 'IPADDDRESS' failed while delivering to the remote domain 'MYDOMAIN' for the following reason: The connection was dropped by the remote host.
I checked SMTPDiag and it comes back:
Error: Expecting "220". Server is not accepting connections.
Failed to submit mail to "server.domain.com"
I checked and my connection control is set to allow and the domains are listed in SMTP.. I am losing my mind trying to figure out why mail is failing at this point..
Are you hitting a rate limit or is your outbound ip on a blacklist? Try the blacklist search here: https://mxtoolbox.com/supertoolmobile.aspx
I'm hoping someone will be able to help me with an issue we are having moving from Test to Production. In test everything is working fine but in Production we are having queue access problems.
Current configuration...
MSMQ queue server located on a work group machine located in DMZ
MSMQ message receiver machine located on a work group machine located off the internal domain
Wcf workflow services hosted in IIS on message receiver machine that monitor the MSMQ queue server
Private queues with names that match the end point of the Wcf workflow service and use the IP address of the queue server, i.e. net.msmq://[IP address]/private/workflowservice/service.xamlx
Net.MSMQ binding in IIS on receiving machine is configured to the IP address of the queue server
Net.MSMQ activator service on the receiving machine is running under NETWORK SERVICE
The receiving workflow services run using an application pool running under NETWORK SERVICE
ANONYMOUS LOGON and NETWORK SERVICE have full permissions on queues
MSMQ server Disable Unauthenticated RPC Calls is disabled
MSMQ installed on both machines
Firewalls are configured to allow ingoing and outgoing on all MSMQ ports
Can send to the queues successfully
If access one of the receiving workflow services via Internet Explorer I receive the following error message,
"An error occurred while opening the queue: Unrecognized error -1072824319 (0xc00e0001)."
I can see from the MSMQ Server machine security event log that the ANONYMOUS LOGON user is accessing the machine but the queue is not being recognised.
Any help would be greatly appreciated.
I have chosen QuteCom SIP client for windows to chat.I have installed and configured the account with my public server. My SIP server is kamailio.The connection to the server is not established. The application is connecting to the server for a long time.
Any help is appreciated.
If looks like keep connecting, then I guess the SIP messages don't get to the server.
You can install Wireshark to monitor traffic on windows host on port 5060 (the SIP port) in order to see if SIP messages are sent to the server.
On server, you can install ngrep for the purpose of seeing if traffic from the phone comes there. The command would be like:
ngrep -d any -qt -W byline port 5060
If you don't see traffic coming to the SIP server, then might be a firewall or an ALG between the client and the server, or, a firewall even on client host or server itself.
If it is something in between (not on client host or server), then you should try to use TCP or better TLS.
Note that if you have the firewall on the server, you will see the SIP packets coming on the network, but they will be dropped by the kernel before getting to application layer. Typically on Linux you can see the firewall rules with:
iptables -L
If the SIP packets come to the server, then set debug=3 in kamailio.cfg, restart kamailio and watch the syslog file (e.g., /var/log/syslog or /var/log/messgaes) for kamailio-specific debug messages -- you should get hints of what happens during processing.
I installed MSMQ on windows server 2008 in workgroup mode. I noticed there is only a private queue and a public queue is missing.
It causes I can't send message from remote computers. I see the messages in outgoing queues. the state is "Waiting to connect" and the Connection History is "No failures reported".
I have two questions:
Can I add the public queue option in any way?
What should I do in order to enable sending message to private queue in remote computer?
(I use WCF.)
Thanks in advane!
On my job we also meet that issue.
The solution was opening the ports that msmq is working with:
TCP: 1801
RPC: 135, 2101*, 2103*, 2105*
UDP: 3527, 1801
Good Luck.