Hi, For me, it may comme from portfast enabled on the switch on which the server is wired. If it is a network link problem for dns resolution, add to your server /etc/hosts the ip/name (in FDQN: ip name.domain name) in for local resolution.
Aurelien Sacha Michel Mallais a écrit : > On Aug 27, 2007, at 1:44 PM, Johann Werner wrote: > >> Am 27.08.2007 um 20:19 schrieb Sacha Michel Mallais: >> >>> On Aug 27, 2007, at 11:03 AM, Pascal Robert wrote: >>> >>>> This is strange, we have a Intel xServe and it seems that we are >>>> the only one who don't have this problem ? >>> >>> We also have an Intel xServe and don't experience this problem, but >>> I think the bug requires 2 things to be exhibited: >>> 1) fast startup time >>> 2) running WO apps on a domain _other_ than the canonical one for >>> the machine >> >> I am using WO on an Intel Xserve with a web domain name that differs >> from the canonical name so I can't confirm that reason. Could it be >> then related to the speed (or lack of speed) of the DNS server? > > Yes, could be, and could be the connection speed between the two, and > even the network stack on the WO server's initialization time (maybe > more local aliases = more startup time). I'm not sure. > > So it appears those conditions are not sufficient... perhaps they are > necessary though: is there anyone experiencing this problem with only > 1 of the 2 conditions above satisfied? > > > sacha > > -- ------------------ Direction des systèmes d'information Université Paris Descartes 01.40.46.17.09 _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-deploy mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
