Clients can't access Web sites created by Web Logic's Web Server
We have Win XP clients that access Web sites created by Web Logic's Web
Server. Occasionally, a user will get a server not found response. We can ping, path ping and
tracert to the server using its name. When the server name is replaced with its IP address, in the
URL, the server still can not be located. So it appears that name resolution is not the issue.
If the user waits a while (15 - 20) minutes, the Web site can be accessed. Rebooting (cold boot)
the work station does not resolve the problem. While this one user is out many others are in the
Web site. If the user goes to one of these workstations, they can successfully login to the Web
site. Any ideas of what could be going on?
One possibility that comes to mind is that the Web server being accessed is set to only
satisfy X number of inbound connections at once. I'm not sure from this description how many
systems are accessing the Web site(s) in question, or whether they are on an internal network or
the Internet at large, but you may want to check and see if the number of inbound connections being
allowed by the Web server is not set too low. This might explain why the server is responding to
pings but not to actual Web connections, and it might also explain the 15-20 minute wait period
(the Web server is waiting for a connection from a particular IP address to expire) -- and why one
user is locked out while others are accessing it.
This was first published in March 2005