Network වැඩකරුවනි උදවු කරපල්ලා

[sihina22]

Machan https:// use karapan

 

[LajjaNathiBayya]

Mu da koheda ban helpdesk eka

na macho. mama client

---

Machan https:// use karapan

enne na ban
------ Post added on Sep 23, 2022 at 12:05 PM

 

[sihina22]

Kawda ban firewall handle karanna. Ubata port address ekak dunne nadda

 

[LajjaNathiBayya]

Kawda ban firewall handle karanna. Ubata port address ekak dunne nadda

ape the hadana auntyda danne na machan.

51615 port eka nam mention karala thiyanawa software eke

 

[LajjaNathiBayya]

ISP la port eka open karanna oneda?

 

[sihina22]

Hari mata machan ip eka ewanna. Web base application ekakda?

 

[amila_mp]

Group Policy ekata gihin New Outbound Rule ekak hadapan IP Adress eke traffic eka unblock wenna.

1. Spoiler: How to Make a Outbound Rule

   Open the Group Policy Management Console to Windows Defender Firewall with Advanced Security.
   [*]In the navigation pane, click Outbound Rules.
   [*]Click Action, and then click New rule.
   [*]On the Rule Type page of the New Outbound Rule wizard, click Custom, and then click Next.
   

   Note: Although you can create rules by selecting Program or Port, those choices limit the number of pages presented by the wizard. If you select Custom, you see all of the pages, and have the most flexibility in creating your rules.

   [*]On the Program page, click All programs, and then click Next.
   [*]On the Protocol and Ports page, select the protocol type that you want to block. To restrict the rule to a specified port number, you must select either TCP or UDP. Because this rule is an outbound rule, you typically configure only the remote port number.
   If you select another protocol, then only packets whose protocol field in the IP header matches this rule are blocked by Windows Defender Firewall. Network traffic for protocols is allowed as long as other rules that match don't block it.
   To select a protocol by its number, select Custom from the list, and then type the number in the Protocol number box.
   When you've configured the protocols and ports, click Next.
   [*]On the Scope page, you can specify that the rule applies only to network traffic to or from the IP addresses entered on this page. Configure as appropriate for your design, and then click Next.
   [*]On the Action page, select Block the connection, and then click Next.
   [*]On the Profile page, select the network location types to which this rule applies, and then click Next.
   [*]On the Name page, type a name and description for your rule, and then click Finish.

 

[kinkon]

බම්ප්

 

[wingman]

ip eka PM.

 

[vito]

I think it would be best if you can post more details regarding the situation you're trying to solve
from what you've mentioned it seems like you're running a local client that's reaching out to a server out in the internet
typically issues like these come up due to an intermediary device (firewall) blocking requests going to a particular port (tcp 51615 in this case since telnet failed)
I doubt it'd due to your local host blocking outgoing traffic. check from the remote end to see if they're receiving your traffic