|
Hi Everyone.
Not sure if anyone met this situation.
I have a program (client) sitting one one computer (WinXP) and a server sitting on another computer (win7). My programs works fine and will not crash when the ethernet cable is pulled out, when the server program is shutdown etc. BUT when the server computer turns off, the client program will crash when trying to connect (it will try to connect to a server every 3 seconds). If the computer is on and even if the server program is not running, the client is fine and will just continue to connect. Not sure what is happening when a computer is off but the ethernet cable is still plugged in.
Has anyone seen this kind of thing? Is there something that I need to do or check for in the client that will prevent this crashing from occurring?
THanks !
Stan the man
|
|
|
|
|
Stan the man wrote: Is there something that I need to do
The first thing I would do is to try some debugging to find out what is causing the crash; and what sort of crash it is. Is it a bug in the client code, something in the system libraries etc? Without that information it's not easy to suggest how to fix it.
Unrequited desire is character building. OriginalGriff
I'm sitting here giving you a standing ovation - Len Goodman
|
|
|
|
|
Code Watson, we need code.
Veni, vidi, vici.
|
|
|
|
|
How long does it take to crash?
As a wild guess...something to do with Active Directory and DNS resolution. Of the scenarios you listed I would suspect that on shutdown AD is told about the server shutdown. Where in the other cases AD doesn't know about it.
Consequently AD fails for the one case where in the others connectivity failures are the result.
Stan the man wrote: the client program will crash when trying to connect <layer>(it will try to connect to a server every 3 seconds)
That is a very small retry window. Presumably you are correctly cleaning up after each of those attempts.
|
|
|
|
|
For debug purposes... did you try to extend the retry (longer than 3 seconds)? Did you make sure the last attempt was finished, failed, and was cleaned up before you attempted to connect again?
3 seconds may not be enough time for the initial attempt to timeout... something to consider.
|
|
|
|
|
Hi All
Is that any simple way to transfer files from one computer to another computer via internet using VC++ code
|
|
|
|
|
Try googling TCP/IP
Why is common sense not common?
Never argue with an idiot. They will drag you down to their level where they are an expert.
Sometimes it takes a lot of work to be lazy
Individuality is fine, as long as we do it together - F. Burns
|
|
|
|
|
I am not sure about the transfer, but a way to get proper answers in CP is not reposting[^]
Regards.
--------
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpfull answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Yes, there is.
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
|
thanks for your reply but i need to sending and receiving data across a internet
|
|
|
|
|
That is exactly what sockets were designed for. Try a Google search and you will find plenty of samples and tutorials that will help you.
Unrequited desire is character building. OriginalGriff
I'm sitting here giving you a standing ovation - Len Goodman
|
|
|
|
|
Okay but i tried many sample socket program it's works fine within a network ips like 127.0.0.1 but i tried to connect dynamic ip( which is get for www.whatismyip.com) it's fails to communicate..
|
|
|
|
|
ravijmca wrote: but i tried to connect dynamic ip( which is get for www.whatismyip.com) it's fails to communicate..
To use IP there are two computers: client and server.
To use IP there MUST be a way to route between those two computers.
To route the address of the server must be exposed to the client. There are ONLY two ways to do that on the internet.
1. The server MUST have a public IP.
2. The server MUST have a network setup (routers/gateways) such that a public IP will route to the server (the server need not have a public IP.)
whatismyip will always give a result but that result doesn't mean anything. All that matters is 1/2 above.
For normal ISPs there are three ways that they provide customers with "internet".
1. The customer has a static public IP.
2. The customer has a dynamic public IP.
3. The customer does not have a public IP. (in this case it does not matter whether it is static/dynamic.)
The result of whatismyip is only relevant to the above if the ISP is 1 or 2. If that is the case then the IP listed is the one that your computer (or router/modem) has.
Note that 127.0.0.1 is not a public IP nor is it a private one for that matter. (Also just because your computer has a public IP it doesn't mean it is public on the internet but it does make it more likely.)
|
|
|
|
|
You forgot to mention the added interference of firewalls into the whole equation.
|
|
|
|
|
anybody can help me...
i have a problem, how to make a file transfer UDP client-server by giving 1 bit error in the file being sent?
|
|
|
|
|
Your question is a bit unspecific. What do you have trouble with? UDP? Using the parity bit thing? Reading a file? What did you try until now?
> The problem with computers is that they do what you tell them to do and not what you want them to do. <
> If it doesn't matter, it's antimatter.<
|
|
|
|
|
|
Why UDP?
UDP does not offer reliability. But In case of file transfer reliability is important.
Are you sure its UDP? not TCP?
|
|
|
|
|
yeah,UDP
I want to create a program that can send the file. but when the file is received the client, a large bit of data is not the same. then resend the request until the server successfully.
if you have the source code in c?
for my coursework ...thank's
|
|
|
|
|
Brillian Kharisma wrote: you have the source code in c?
for my coursework
All the more reason for you to do it yourself. Ask us specific questions about specific code problems to help you. No one here is going to do it for you.
Why is common sense not common?
Never argue with an idiot. They will drag you down to their level where they are an expert.
Sometimes it takes a lot of work to be lazy
Individuality is fine, as long as we do it together - F. Burns
|
|
|
|
|
UDP is NOT typically used for file transfers because it's not reliable. If you add parity, you can detect errors and request resends, but you're just replicating TCP at that point.
Brillian Kharisma wrote: if you have the source code in c?
for my coursework ...thank's
You need to do your own homework. Sorry.
|
|
|
|
|
The only advantage you gain from UDP is speed. I use UDP for realtime hardware status updates but I never use it to transfer files. Why not use TCP as others have suggested. It was designed for streaming files. You could also check out named pipes.
|
|
|
|
|
I want to get two front and profile picture of a person then make 3D Head model of it using Visual C++ and openGL.
How could I start?
|
|
|
|
|
Look Creating 3D Head model open GL C++here[^]
You talk about Being HUMAN. I have it in my name
AnsHUMAN
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
