Hosting and Servers

12-Mar-13 12:58

hey !
its a question to me, can we use our pc as a virtual server!?
for more details i must say , i made a chat windwos application include 2 part, server and client ! well i want know can i put server part in my pc and give client to my friend, then my pc play virtual server role and client connect to my pc and act with the server part that is in my pc(virtual server) .
if we can do this, then how?
very thanks all!

Richard MacCutchan12-Mar-13 22:29

Richard MacCutchan

12-Mar-13 22:29

Assuming your server and client can communicate across the internet then it should work.

Use the best guess

Albert Holguin13-Mar-13 5:41

13-Mar-13 5:41

It's just a regular server-client setup, all you need is for the client to have the IP address of the server and to have the ports used available and unrestricted (firewalls in between might block).

ali_heidari_13-Mar-13 5:44

13-Mar-13 5:44

so you think just should set ip server in client part, as my own ip?
i tried it ... no resault!
i found must have a valid ip, but i dnt know how provide a valid ip also how set it on my pc!

Albert Holguin13-Mar-13 5:49

13-Mar-13 5:49

Usually when you pay for internet service, your ISP sets your IP address and you can't really change it (most of the time it's not really static either so it might change every now and then), you can visit certain websites to see what your external IP address is.

ali_heidari_13-Mar-13 5:51

13-Mar-13 5:51

i know whats my ip adress, and i knew ip can be eithier static or dynamic !
im tryin to say that when in my tcp client application i set my ip for endpoint, it doesnt connect to my pc!

Albert Holguin13-Mar-13 7:13

13-Mar-13 7:13

No need to use exclamation points, it's not my fault you can't express yourself clearly and I'm only helping you out of the kindness of my heart so be polite.

- Check to make sure the route exists.
- Make sure ports aren't being blocked.
- Check logs on firewalls and the application.

ali_heidari_13-Mar-13 8:29

13-Mar-13 8:29

i did not shout on you body!anyway i am sorry if i did not talk well!
thanks for your guidance!

Vasudevan Deepak Kumar31-Mar-13 4:49

Vasudevan Deepak Kumar

31-Mar-13 4:49

Too much of exclamation points in lieu of periods and commas send a wrong signal/message.

Vasudevan Deepak Kumar
Personal Homepage
Tech Gossips

The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep!

windows firewall

karimi55559-Mar-13 7:08

karimi5555

9-Mar-13 7:08

How can i block internet access of some clients and allow to some with windows firewall?

Re: windows firewall

Albert Holguin13-Mar-13 5:39

VPN Ports Required to be Opened

13-Mar-13 5:39

Can you clarify what you're trying to accomplish. Your question doesn't really make sense as to your setup and what it is exactly you're trying to accomplish.

Do you have a server that people access over the internet? If so, what services does your server provide? In this scenario, yes, you can allow certain IP addresses through your firewall and block everyone else but depending on your service, you can also do it at the application layer.

Richard Andrew x644-Mar-13 14:59

Richard Andrew x64

4-Mar-13 14:59

For PPTP, I know I need to open port 1723, but the error message I'm getting when trying to connect says I need to enable GRE (Generic Routing Encapsulation.)

Does this mean opening an additional port? And what port would that be?

The difficult we do right away...
...the impossible takes slightly longer.

Re: VPN Ports Required to be Opened

Jörgen Andersson5-Mar-13 7:19

Jörgen Andersson

5-Mar-13 7:19

No it's not a port, GRE is a protocol just like TCP. And where TCP is number six and UDP is seventeen, GRE is number 47[^].

You need to dig into the manual of your firewall to find out how to enable that protocol

"The ones who care enough to do it right care too much to compromise."
Matthew Faithfull

Re: VPN Ports Required to be Opened

Richard Andrew x645-Mar-13 9:27

Richard Andrew x64

5-Mar-13 9:27

Thanks!

The difficult we do right away...
...the impossible takes slightly longer.

IIS and possible load

n.podbielski4-Mar-13 1:55

n.podbielski

4-Mar-13 1:55

I don't know if this is right place to ask but I did not saw any better.

Maybe someone with high demand web sites experience can tell me where is factor for concurrent connection to IIS, when it finally give up and fails? I read some time ago that on web there is 10k problem, when any HTTP server on the market cannot handle that. It is to much IMHO for corporate complex web apps with 3 tiers and high MSSQL usage. I have found that this is approximately 1000 connections at the same time, but it still seems like too much. I cannot imagine 1000 CRUD sqls on MSSQL. Usually for single HTTP requsts there is at least 3 sql requests, usually more. So how much connection web app would handle? 100? Seems more likely, but still in my prevoius work, there was application that had hard time providing for few dozens users and abviously they not always requaired server to do something.

Any one has experience with the point when you start to need not 1 but 2 IIS servers?

No more Mister Nice Guy... >: |

Eddy Vluggen5-Mar-13 5:06

Eddy Vluggen

5-Mar-13 5:06

IIS is not "limited" to a certain number of connections, and SQL Server should not run out of them; there's a pool, and processing is halted until there's an item available from the pool.

What caused this question? Performance-problems, or concurrency-problems?

Bastard Programmer from Hell Suspicious | :suss:

If you can't read my code, try converting it here[^]

n.podbielski5-Mar-13 6:50

n.podbielski

5-Mar-13 6:50

Primarily lack of knowledge about this topic.
Secondly is requirement of new project: it has to be prepared to work on IIS web farm. I know that load balancing make sense with high-load applications. This is the reason for this question. Where is threshold for IIS when you have to switch from 1 web server to 2 or more to maintain high response times under high-load. I suspect this is dependent from complexity of code, so let's assume that it is complex and not optimal.
Also I know that IIS and MSSQL have no hardcoded limit of, lets say 101 connections, and when 102 users decide to open page, it's gonna say to him: 'no way dude!' and gonna send HTTP Code - Service Unavailable.
But there have be some kind of queue of connections and when this queue will be adding more requests then server can handle it's gonna shut itself down eventually, right?

I don't want to know exact number as it is impossible without proper stress testing of whole environment, but just a factor should be enough. Is it 10? 100? 1000? 10k?
I heard about 10k problem before but I don't know if this still an issue with all this xCore xGHz x0GB RAM server as we have now, and sources are dated: http://en.wikipedia.org/wiki/C10k_problem[^]

No more Mister Nice Guy... >: |

Eddy Vluggen5-Mar-13 9:29

Eddy Vluggen

5-Mar-13 9:29

n.podbielski wrote:
I suspect this is dependent from complexity of code, so let's assume that it is complex and not optimal.

It's also dependent on the hardware (server and network), some IIS-settings, the "size" of your average file, and the general state of your servers' OS.

n.podbielski wrote:
But there have be some kind of queue of connections and when this queue will be adding more requests then server can handle it's gonna shut itself down eventually, right?

AFAIK, it doesn't shut down. If the client doesn't get a response within a set time, he'll get a time-out. Just like in a DDOS-attack, so to speak. The server processes what it can, within the limits of it's hardware.

n.podbielski wrote:
I heard about 10k problem

I didn't, so I'm gonna shut up and hope that some other reader can contribute some insight into the topic.

Bastard Programmer from Hell Suspicious | :suss:

If you can't read my code, try converting it here[^]

Vipin Pandey18-Mar-13 4:08

Vipin Pandey

18-Mar-13 4:08

Hi

Please read this for IIS Connection :

By default IIS7 has a limit of handling 12 concurrent requests per CPU and will queue requests above this limit. If you have some significant web load and many AJAX style requests to your server – this setting maybe very restrictive and it is hard to find out the root of the problem when you server performance is suddenly degraded.

See this post to get the picture how it can cause performance issues on your server.

Some relevant info about asp.net thread usage on IIS7 here:

asp.net thread usage on IIS7 and IIS6

Thomas Marquardt advice is to change this default limit. Recommended settings:
“All of this may be a little confusing, but for nearly everyone, my recommendation is that for ASP.NET 2.0 you should use the same settings as the defaults in ASP.NET v4.0; that is, set maxConcurrentRequestsPerCPU = “5000″ and maxConcurrentThreadsPerCPU=”0″.

This is done by adding DWORD MaxConcurrentRequestsPerCPU to the registry under

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ASP.NET\2.0.50727.0

called MaxConcurrentRequestsPerCPU (DWORD). This key doesn’t exist by default. Or/and in aspnet.config section which overrides registry setting (also doesn’t exist by default) aspnet.config is here on windows 64bit:

%windir%\Microsoft.NET\Framework64\v2.0.50727\aspnet.config

You need to add the following section under “configuration” section (here I used default values) – don’t forget change maxConcurrentRequestsPerCPU to 5000.

< system.web>
< applicationPool
maxConcurrentRequestsPerCPU="12"
maxConcurrentThreadsPerCPU="0"
requestQueueLimit="5000" />
< /system.web>