Howto reregister a Windows Server in Appletalk Zone?

[Kendall Link]

I have been looking for a way to force a Windows 2000
Server that has Appletalk running to re-register itself
in a appletalk zone without having to reboot the
computer. Does anyone know how to do this?

Thanks,
Ken

 

[William M. Smith]

I have been looking for a way to force a Windows 2000
Server that has Appletalk running to re-register itself
in a appletalk zone without having to reboot the
computer. Does anyone know how to do this?

Hi Ken!

I'm not in front of a Windows 2000 server to verify whether or not it needs
to be restarted, but if it tells you to restart you shouldn't fight it.

To select the zone that your server will participate in, you'll right-click
My Network Places --> Properties, right-click the appropriate adapter -->
Properties. Select the Appletalk protocol and click the Properties Button.
Here, you can select the zone. Again, I'm not sure if you'll be required to
restart, but if you're instructed to do so, you should.

Since the Mac File Services are applications sitting on top of Windows
server, the most you should have to do is simply stop and restart the Mac
File Service itself and not the entire server.

Hope this helps! bill

 

[Kendall Link]

Thanks for the reply William. Well, its not that the
system is asking to reboot... what happen is during the
blackout we shut down all of our servers. When the power
came on, we turned on our NT 4 system that is acting as
our seed router for our appletalk networks. We then
powered up our Win2k systems that then register
themselves in the Appletalk zone against the seed
router. Well, sometime after that point the seed router
got rebooted and the only Windows 2000 servers that are
registered in the chooser were servers that were rebooted
after the seed router came up the second time. What I
was wondering is if you look in the event log of a system
with appletalk running on it there is an event that says
something like "successfully regestered computer on
appletalk zone blah blah". I was wondering if there was
any way to, for instance, stop and start the appletalk
service (if there was one) that would cause the Windows
2000 server to re-register itself in the zone against the
seed router?

If not I should be able to schedual a reboot for late
saturday night but I thought I would check to see if it's
possible to do it without a reboot.

Thanks for any help,
Ken

-----Original Message-----

 

[William M. Smith]

Thanks for the reply William. Well, its not that the
system is asking to reboot... what happen is during the
blackout we shut down all of our servers. When the power
came on, we turned on our NT 4 system that is acting as
our seed router for our appletalk networks. We then
powered up our Win2k systems that then register
themselves in the Appletalk zone against the seed
router. Well, sometime after that point the seed router
got rebooted and the only Windows 2000 servers that are
registered in the chooser were servers that were rebooted
after the seed router came up the second time. What I
was wondering is if you look in the event log of a system
with appletalk running on it there is an event that says
something like "successfully regestered computer on
appletalk zone blah blah". I was wondering if there was
any way to, for instance, stop and start the appletalk
service (if there was one) that would cause the Windows
2000 server to re-register itself in the zone against the
seed router?

If not I should be able to schedual a reboot for late
saturday night but I thought I would check to see if it's
possible to do it without a reboot.

Hi Ken!

Verrry interesting problem. I can only give you speculation on this one.

Zones are a function of the Appletalk protocol and protocols can't be
stopped or started by any means that I know of. But they can be unbound and
bound to the network adapters.

While viewing the Appletalk protocol among the clients and protocols
properties of the network adapter, you could try unchecking the Appletalk
protocol and closing out the properties window to save the change. Then you
could go back in and recheck the Appletalk protocol and see if this allows
you to reselect the Appletalk zone when you click the Properties button for
the Appletalk protocol.

Binding/unbinding protocols shouldn't require a restart of the server and
you're not going to lose any Appletalk connectivity for the server if it
didn't have any to begin with.

What are your thoughts?

bill