Buy Microsoft Office Home & Student
Networking & wireless: The semaphore timeout period has expired.
The semaphore timeout period has expired.
by john.breen - 8/11/04 8:12 AMWe are getting this message - more often on Mondays, but we got it today (Wed) on a system when trying to access a network resource.
We have 5 computers, 1 of which sits idle and acts as a "server." Some client computers get turned off at night, others do not. All are running both ZoneAlarm and NAV. We are using a DSL modem, Netgear switch and Linksys router.
About 3 weeks ago, we found that we were getting the above message when trying to access shared folders on the server. Not all computers misbehave - the problem occurs on different ones on different mornings. When a system does have the problem, it can still access other shared resources (on other client computers) with no problem. It can also ping the "server" with no problem. The clients which fail are both XP and W2K systems. The ONLY way we have found to get these connections restored is to reboot the server system. Rebooting the problem clients does nothing.
I've read that this may have something to do with "renewing IP addresses".
Any suggestions (in plain English)?
Thanks a ton in advance,
John
Re: The semaphore timeout period has expired.
by R. Proffitt
- 8/11/04 8:18 AM
In reply to: The semaphore timeout period has expired. by john.breen
If the server is the one handing out the DHCP information, rebooting it may be a sign the server needs attention.
Nothing in your post tells any other clue.
I'd look at what is the DHCP server. But as lightwieght your post is, all I can write is where the issue appears to be and nothing more.
bob
Re: The semaphore timeout period has expired.
by john.breen - 8/12/04 6:06 AM In reply to: Re: The semaphore timeout period has expired. by R. Proffitt
Sorry for the lack of tech info.
Our router is the one acting as the DHCP server. That Linksys was replaced with a new, wireless Linksys and that didn't solve a thing.
About the new box...
by R. Proffitt - 8/12/04 6:43 AM
In reply to: Re: The semaphore timeout period has expired. by john.breen
A new product doesn't mean the device has the latest firmware. And something else...
For example, I picked up a new Dlink. It would not connect to the ISP or hand out Wifi DHCP information. At first I thought "what a piece of junk". But then I remembered to check the firmware and sure enough there was new firmware. Said device is now just fine all around.
Next, since you are using the linksys as the DHCP server, is it on the UPS so you know it's not subject to brownouts and odd power outages?
In closing, if some other DHCP server is on the network, then you could have a design issue to deal. And finally, when I see this, I take a laptop to the linksys (or other) and jack right into it's ports to see if I can get a DHCP linkup. If not, I power cycle the linksys to see if that was the issue. So far only one replacement due to that.
Bob
Re: About the new box...
by john.breen - 8/13/04 4:28 AM In reply to: About the new box... by R. Proffitt
Bob,
Thanks for the suggestions. Unfortunately, none of these issues is of concern (they have all already been addressed). Since it is only this one computer that is inaccessible at times, I lean towards something having changed on it - like a Windows Update or ZoneAlarm update which is aggravating things. Pain in the butt.
J
Only one PC.
by R. Proffitt - 8/13/04 8:47 AM
In reply to: Re: About the new box... by john.breen
In that case, look to see if they let Windows Update install a driver. If so, you've found it.
As to Zone Alarm, you are on your own. I have to remove it and use the native NT/2000/XP/2003 firewall when I see such.
Zonelabs had support for such.
Bob
| Forum legend: | |
 |
Locked thread |
 |
Moderator |
 |
CNET staff |
 |
Samsung staff |
 |
Norton Authorized Support team |
 |
AVG staff |
 |
Windows Outreach team |
 |
Dell staff |
 |
Intel staff |
