TCP Port Blocking by Firewall and Application Hanged

  • Thread starter Thread starter Eddie Leung
  • Start date Start date
E

Eddie Leung

Hi All,

I have a critical problem and don't know how to solve. Please help.

My company now configures the firewall to port the blaster port on 4444 and
1434 to prevent again blaster worm. However, some applications will be
dynamically allocated tcp ports to communicate to server, the assigned port
numbers start from 1024 to 65535, when the ports be assigned are 1434 or
4444, both application and the machine running application are hanged. How
can I solve this problem? Can I configure the machine so that the port 1434
and 4444 will not be assigned for communication used?

Thanks in advance.

Regards,

Eddie
 
if your IT people are blocking connections FROM port 4444 on your machine
then they don't understand the problem, or they don't know how to set up
routers to block the worm properly. the worm listens on 4444, it doesn't
generate traffic from 4444. they want to block connections made TO port
4444. the same goes for 1434, traffic is directed TO port 1434 not from it
so they should not block connections from your machine's port 1434 to
anywhere. they should probably concentrate on getting all the proper
patches onto machines rather than trying to block every little port on a
network and messing up proper communications.
 
Hi,

But if they can't accept this approach and still block the ports, what is
the alternative? Any configuration I can set to disable to use these two
ports?

Thanks.

Regards,

Eddie
 
you could start some other app using those ports, that should make the
automatic port assignment skip over them for outgoing connections.
otherwise i don't know of a way. if you get an app that fails that you
think is because of that just shut it down and try again, most will take the
next higher numbered port which then may work. but someone should educate
your IT people about the error of their ways.
 
Back
Top