Microsoft SQL Server error53 with remote connection

  • I am trying to connect to my database remote, for now I just trying to connect to it with ip on same computer, but I got error 53(on the photo). First I want to know is this the right place to ask this question, I tried every possible solution that I found and I haven't any idea what more to make.

    Attachments:
    You must be logged in to view attached files.
  • What have you tried so far to debug?

    The most likely solution for this is firewall configurations need putting in place.

    ensure there is an exception for the correct tcp/udp ports in the windows and any other hardware and software firewalls between your client and the server.

  • I have added rule in the windows firewall, I have Avast too, but I don't know how to add rule to it and just disable it for 1 hour when trying to connect. My TCP/IP are enabled everywhere in SQL server configuration. I tried everything in internet and I don't know how to make it to work. The only thing that I am not sure is the forwarding the address in the router settings, I watched video in youtube where they added it (picture 3), but my router (image 4) has different control panel and I am not sure for this. If I set with the settings in the picture I get error "The IP address is not in the same subnet with the LAN" and I can set only the last digits 192.168.1.xxx

    Attachments:
    You must be logged in to view attached files.
  • When you state you are working remote - what exactly does that mean?  Are you trying to access servers on a corporate network from home?  If so - you cannot get to the servers on the corporate network directly, you would need a VPN set up to connect you to that network.

    If you are doing something else...can you explain further?

    Jeffrey Williams
    “We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”

    ― Charles R. Swindoll

    How to post questions to get better answers faster
    Managing Transaction Logs

  • No, its just my pc, and I want to access the database remotely from second pc. The both pc are not in same network.

  • If the PC's are not on the same network - how are you going to connect to the other PC?  You have to be able to define a route to/from the PC's over a network and if that doesn't exist there is no way to connect.

    Jeffrey Williams
    “We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”

    ― Charles R. Swindoll

    How to post questions to get better answers faster
    Managing Transaction Logs

  • They will connect via IP

    https://youtu.be/jgWOZT6za3g?t=736

    • This reply was modified 4 years, 8 months ago by urkqsrk.
  • urkqsrk wrote:

    They will connect via IP

    https://youtu.be/jgWOZT6za3g?t=736

    If they are not on the same network - it doesn't matter.  You cannot connect to an IP address on another network unless there is a path defined from your network to that other network.

    All a network is - is a wire between 2 (or more) computer systems.  That wire can be the internet - a business network - a home network or even bluetooth connections...but there must be a path to get data from one system to the other.

    Since these machines are on different networks and there is no defined path between them - there is no way to connect them to each other.

    Where is the PC with SQL Server installed and running?  Where is the PC you are using to try an connect to SQL Server?

    How does the first PC connect to its network?  How does the second PC connect to its network?

    Jeffrey Williams
    “We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”

    ― Charles R. Swindoll

    How to post questions to get better answers faster
    Managing Transaction Logs

  • The first pc is my home pc, and the second is on my work place. I thought with just IP I can access the SQL DB with my second pc .

  • You would need to make your SQL server public internet facing, which in this day and age is NOT a good thing to do with all the data breaches etc.

    If your at home and your SQL server is in the Workplace then you should be using proper workplace security access methods like VPN's so you are essentially sitting within the workplace network.  Your just setting yourself up to be devastated by data protection lawsuits and other things if you make it publicly available over the internet.

     

Viewing 10 posts - 1 through 10 (of 10 total)

You must be logged in to reply to this topic. Login to reply