Re: Socket timeout
- From: Chuck <none@xxxxxxxxxxx>
- Date: Fri, 21 Apr 2006 12:17:13 -0700
On Fri, 21 Apr 2006 10:59:02 -0700, Mummy <Mummy@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote:
The scenario is as follows:
There are three desktop computers let's call them S, C1 and C2, and I've
connected to the network my Laptop let's call it L.
All computers are running WinXP SP2.
All computers can see each other's shared files.
On the firewall of all computers three ports are opened. Custom ports for my
ypplication (17021 and 17022) and registered port for Interbase (3050).
Computers C1 and C2 can not connect to S through any of the three ports
mentioned above (I always get the timeout message 10060)
Computer S can access both C1 and C2 through all of those ports...
C1 can access C2 and also C2 can access C1 through those three ports...
L can access all computers and all computers can also access L through those
three ports.
So basically any computer can access any other computer, except C1 can not
access S, and C2 cannot access S.
Short diagram:
C1 -X-> S S ----> C1
C2 -X-> S C2 ----> C1
L ----> S L ----> C1
C1 ----> C2 C1 ----> L
S ----> C2 C2 ----> L
L ----> C2 S ----> L
I even tried disabling Windows firewall, but it's the same...
Can somebody please answer me what is hapenning, and how do I get to the
bottom of that problem, and in the end how do I solve it?
I must mentin that C1 and C2 are identical Hardware configurations, but
differ from S and L.
Most of the experience here is with Windows Networking, and file sharing. And
errors like a 10060, "...connection failed because connected host has failed to
respond..." are generally known to be caused by LSP / Winsock corruption. Your
asynchronous access / visibility symptoms can also result from this.
<http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html
If not LSP / Winsock corruption, the next candidate for cause of this problem
would be a misconfigured or overlooked personal firewall, or other security
component. Windows Firewall is not the only possible culprit. There are several
other possibilities too, and any might be the cause of your problem. Read this
article with an open mind.
<http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html>
http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html
Do you have similar problem (or a conflicting, lack of problem) between your
computers, with actual file access? Have you tried file access?
--
Cheers,
Chuck, MS-MVP [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.
.
- Prev by Date: Re: Approach to use cross-over connect as part of LAN
- Next by Date: Re: network speed question
- Previous by thread: network speed question
- Next by thread: Re: Socket timeout
- Index(es):
Relevant Pages
|
