Re: (Software) timeserver for windows being broadcast-able incl. keys

Erik wrote:

What I do understand is that the difficulty is in the combination of
broadcast-time-correcting inchangeable
(broadcast-)clients on different network segments by one server

It's independent of NTP or anything related to time. The difficulty
is with using broadcast with this network design, regardless of what the
application is. And it's not so much that you have a single server, but
that you have only a single interface that is not on any of the 4 networks
in which you are interested.


What I still would like to know:

Is the following (earlier posted) idea...

broadcast 145.47.51.127 key 1
broadcast 145.47.51.255 key 1
broadcast 145.47.52.127 key 1
broadcast 145.47.53.127 key 1

..from server...

IP-adres . . . . . . . . . . . . . . .: 145.47.54.146
Subnetmask . . . . . . . . . . . .: 255.255.255.128
Standaardgateway . . . . . . . .: 145.47.54.129

... definetely useless or still worth a try?

Definitely useless.


BTW: the manufacturer advises to install its systems in the same
network segment behind a router to be coupled with the company-VLAN
The time server, being on the same router, will be able to reach all
clients by broadcast
Yet, here we do not have networks-per-manufacturer but mixed networks,
resulting in a network with systems of this manufacturer
spread across the whole network (which is divided into several
subnets)

The key thing to know here is whether each subnet is on its
*own* VLAN or if they are all on the *same* VLAN. If they and
the server are all on the same VLAN, it may be possible
to make broadcast work even with only one server interface.

It may also be possible to make it work if the routers are
configured to route broadcast packets to networks other
than the one they originate on.

If neither of the above is true, which is most likely the case,
I think the only way to make broadcast work would be:

a) Put a server on each of the 4 subnets. You can peer the
4 servers together in NTP. In this case, each server would
broadcast only to its own subnet.

-OR-

b) Put 4 NICs in the server you have, and wire each NIC to
one of the 4 subnets, giving each an address on its own subnet
instead of the address your server has now. In this case, the one
server would broadcast to all 4 subnets using the broadcast
statements you listed above.

-Tom
.

Relevant Pages

  • Re: Multi NIC Windows 2003 routing problem
    ... You cannot use two IP#s from different subnets on the same NIC unless it is ... > All network traffic destined for the 192.168.20.x and 192.168.90.x should ... (still does, but that server has to go, for obvious reasons). ... >> Microsoft Windows XP - Multihoming Considerations ...
    (microsoft.public.win2000.networking)
  • Re: dhcp server - one mac on multiple subnets
    ... same physical network (a multihomed server). ... The network topology looks like this (with some 20 subnets): ... distinguish on which subnet of a shared network a client should boot. ...
    (Debian-User)
  • Re: Problem with ListAvailableSQLServers in vb 6
    ... With EnumSQLSvr.exe, it doesn't work (when I remove the network cable, I ... With SQL Server 2000, a Win98 computer is in the list ... > can you please verify your local MSDE instance has network protocols enabled ... > relative instance will not be enlisted in the broadcast call for server ...
    (microsoft.public.sqlserver.msde)
  • Authentication problem?
    ... How can I check on this broadcast issue you're ... are your network configuration correct. ... >>logging into a W2k server with Active Directory. ... >>from a domain login to a home login and back to a domain ...
    (microsoft.public.win2000.security)
  • Re: Windows XP network problem...
    ... Look into setting up a DHCP server utilizing DDNS to resolve host names ... across multiple subnets. ... But, if you have pre-windows 2000 machines, then you're pretty much ... > Windows recognizes names instead of IP addresses for network requests, ...
    (microsoft.public.win2000.networking)