locked
No access to any non-default application from network WS2019 RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi.

    Trying to handle such issue: have two apps that need to be accessed in internal network. Default Windows services like RDP or SMB are accessible and working good, but not others. Got every required port opened, and even tried to disable firewall at all - nothing changes. Network type is Domain. 2 NICs are teamed in switch-independent mode. Server has static IP and all other PCs are in same subnet.

    What have I already done:

    1. netstat - tells both apps are in LISTENING state on the 0.0.0.0 interface (and are accessible locally on the server, but not from the network)

    2. nmap - tells that port is filtered

    3. telnet to port - connection failure

    4. installing both apps on a client Windows machine - both apps are perfectly accessible from that machine, so I assume that's some Windows server or maybe double NIC problem.

    How can I determine what causes the problem?

    Wednesday, March 18, 2020 8:16 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Can you ping the IP of the server from others?

    We suggest that you can use telnet x.x.x.x in cmd to see if the connection is successful.

    Please post the results of the command so that we can analyeze the problem for you.

    Note: since this is a public forum, everyone could view your information, please remove private information that might leak your privacy.  

    Hope this can help you, if you have anything unclear, please let me know.

    Have a nice day!

    Allan

    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, March 19, 2020 2:40 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi.

    Yes, I can ping server from other machines. As I said, default services like RDP are accessible well. Telnet itself is disabled on the server so telnet 192.168.0.100 returns connection failure on port 23. Same for telnet 192.168.0.100 13000 (13000 is the required TCP port to be connected).

    Thursday, March 19, 2020 3:28 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Please try the following steps:

    1. Click the Start menu then search for/select Windows Firewall.
    2. Select Advanced Settings.
    3. Select Inbound Rules from the left hand pane
    4. Under Inbound Rule Actions. select New Rule.
    5. For the Rule Type select Port, click next, then select TCP and Specific Local Ports.
    6. Enter 23 for the port number and click next.
    7. Select Allow Connection then click next.
    8. Specify when the new rule can be applied. (Domain, Private, and Public)
    9. Give the Inbound Rule a name such as "Telnet" then click finished.

    Hope this can help you, if you have anything unclear, please let me know.

    Have a nice day!

    Allan

    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, March 19, 2020 9:46 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    What I have discovered so far: tried to break the bridge and just use two interfaces, the connection to those apps are perfect now, so the problem is bridging. Now I have another question - why bridge causes that problem? And is that worth to use it?
    Friday, March 20, 2020 3:31 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Because using the interface can access the host from different IPs and connect the interface you need.

    But the nature of bridging is based on MAC addresses rather than IP.

    So you may not be able to access it over a simple network.

    Hope this can help you, if you have anything unclear, please let me know.

    Have a nice day!

    Allan

    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, March 23, 2020 7:48 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Just checking in to see if the information provided was helpful.

    Please let us know if you would like further assistance.

    Best Regards,

    Allan

    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, March 26, 2020 8:30 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    So a good working bridge is only possible when it is configured in a switch, so all network knows about it not just the server?
    Wednesday, April 8, 2020 5:47 AM