Tcp/IP issue C# with SQL server 2008

Question

0.00/5 (No votes)

See more:

Using a C# Windows client/server application with SQL Server.

On the SQL Server machine, I enabled TCP/IP in networking and wrote inbound firewall rules to access the database.

On the client machine, I added outbound firewall rules to access server, and it worked.

But now suddenly, the client machine stops responding, and throws an error

What I have tried:

error message:

Can't to find mentioned TCP host

Posted 22-Jun-20 19:22pm

Rajasekaran Bose

Updated 22-Jun-20 20:43pm

Add a Solution

Comments

RedDk 24-Jun-20 8:16am

Quote: "throws an error".

It might be helpful to tell cpians what kind of error this is (crashes the machine, blue-screens the machine, shows up in computer Management under Event Viewer, etc) or, if a textbox with an actual error message appears on screen, the exact text of this "error". I see TCP host is mentioned but to be honest I've never seen TCP host errors in the flesh only through ditched processes stepping out of rolled-over "SQL Server Configuration" regurgitations where zombies like "Named Pipes" and "Shared Memoory" come at you as if they would eat your enabling brains.

Also antivirus programs (typically third-party but of late native) make it a habit of flexing port address coding muscle by making it possible to prescribe to hard-wired digits. Like 'yer 1433.

Rajasekaran Bose 25-Jun-20 1:58am

I using windows 7 os on server machine. and using Windows 10 on client machine. Is there any chance to firewall and connectivity problem for this?

1 solution

Add a Solution

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2020-06-22T20:44:00

We can't fix that for you - you need to start looking at your network and the names / IP addresses you have assigned.

If you are connecting to a WLAN / LAN based SQL Server machine via an IP address, then you need to check that the IP address of that machine has not changed - most routers issue them on a first-come-first-served basis so if the router is power cycled the Server may not get the same IP address again (this is called Dynamic addressing). It is possible to set routers to always allocate the same IP address to a specific machine (called Static Addressing), but the "how" of that varies from router to router.

A much better idea is to connect via a name rather than an IP address.

Tcp/IP issue C# with SQL server 2008

1 solution

Solution 1

Add your solution here

Preview 0

Tcp/IP issue C# with SQL server 2008

1 solution

Solution 1

Add your solution here

Preview 0

Existing Members

...or Join us