Home › Forums › OS X Server and Client Discussion › Questions and Answers › Mac OS X Server loses connectivity w/o constant ping
- This topic has 5 replies, 2 voices, and was last updated 21 years, 7 months ago by
discogravy.
-
AuthorPosts
-
March 27, 2005 at 3:11 am #361096
discogravy
ParticipantI have a user that is running a server (Mac OS X on a G4) in the DMZ of my network. He had rendezvous turned on and we noticed that the DMZ was getting UDP broadcasts from his box; since he wasn’t using it and it was affecting the whole segment, I asked him to turn off Rendezvous. Since this has happened, if he doesn’t run a constant ping, his server loses connectivity. The box does not appear to have any hardware failure and is fully patched w/ the latest os x server. What could be causing this? I’m stumped; I’ve also posted this over at experts-exchange.com (here) if anyone here’s a member there and wants to earn a quick 500 points.
March 28, 2005 at 1:09 pm #361110alxknt
Participanthave you confirmed that it is rendezvous’s fault; have you tried turning rendezvous back on to see if the machine’s connection stabilises ?
how exactly did you manage to turn off rendezvous? did you just un-tick the ‘Enable Rendezvous registration’ in the AFP settings?
March 28, 2005 at 2:40 pm #361111discogravy
Participantalxknt wrote:
have you confirmed that it is rendezvous’s fault; have you tried turning rendezvous back on to see if the machine’s connection stabilises ?
how exactly did you manage to turn off rendezvous? did you just un-tick the ‘Enable Rendezvous registration’ in the AFP settings?
I do not believe that the loss of connectivity is due to Rendezvous, rather that when it was on, it’s periodic broadcasts were keeping the machine online. It was turned off via the gui, yes.
March 28, 2005 at 2:43 pm #361112discogravy
ParticipantMacTroll wrote:
How did you turn of Rendezvous?
Via the GUI in the services section (sorry I can’t be more specific, it was a few weeks ago, and I am not the admin of that box.)
March 29, 2005 at 8:47 pm #361133discogravy
Participantspanning tree was enabled on the port that the server was connected to on the switch. disabling it seems to have fixed the issue.
April 2, 2005 at 1:42 am #361169discogravy
Participanttha’ts what we wound up doing; switching the port on the switch from spanning tree to portfast
-
AuthorPosts
- You must be logged in to reply to this topic.