Category: ntp server

Keeping a Windows 7 Network Secure, Reliable and Accurate

  |   By

Many modern computer networks are now running Microsoft’s latest operating system Window 7, which has many new and improved features including the ability to synchronise time.

When a Windows 7 machine is booted up, unlike previous incarnations of Windows, the operating system automatically attempts to synchronise to a time server across the internet to ensure the network is running accurate time. However, while this facility is often useful for residential users, for business networks it can cause many problems.

Firstly, to allow this synchronisation process to happen, the company firewall must have an open port (UDP 123) to allow the regular time transference. This can cause security issues as malicious users and bots can take advantage of the open port to penetrate into the company network.

Secondly, while the internet time servers are often quite accurate, this can often depend on your distance from the host, and any latency caused by network or internet connection can further cause inaccuracies meaning that you system can often be more than several seconds away from the preferred UTC time (Coordinated Universal Time).

Finally, as internet time sources are stratum 2 devices, that is they are servers that do not receive a first-hand time code, but instead receive a second hand source of time from a stratum 1 device (dedicated NTP time server – Network Time Protocol) which also can lead to inaccuracy – these stratum 2 connections can also be very busy preventing your network from accessing the time for prolonged periods risking drifting.

To ensure accurate, reliable and secure time for a Windows 7 network, there is really no substitute than to use your own stratum 1 NTP time server. These are readily available from many sources and are not very expensive but the peace of mind they provide is invaluable.

Stratum 1 NTP time servers receive a secure time signal direct from an atomic clock source. The time signal is external to the network so there is no danger of it being hijacked or any need to have open ports in the firewall.

Furthermore, as the time signals come from a direct atomic clock source they are very accurate and don’t suffer any latency problems. The signals used can be either through GPS (Global Positioning System satellites’ have onboard atomic clocks) or from radio transmissions broadcast by national physics laboratories such as NIST in the USA (broadcast from Colorado), NPL in the UK (transmitted form Cumbria) or their German equivalent (from Frankfurt).

How the Moon Affects Time on Earth

  |   By

We take it for granted that a day is twenty-four hours. Indeed, our body’s circadian rhythm is finally tuned to cope with a 24-hour-day. However, a day on Earth was not always 24 hours long.

In the early days of the Earth, a day was incredibly short – just five hours long, but by the time of the Jurassic period,  when dinosaurs roamed the Earth, a day had lengthened to about 22.5 hours.

Of course now, a day is 24-hours and has been since humans evolved, but what has caused this gradual lengthening. The answer lies with the Moon.

The moon used to be a lot closer to the Earth and the effect of its gravity was therefore, a lot stronger. As the moon drives tidal systems, these were a lot stronger in the early days of the Earth, and the consequence was that the Earth’s spin slowed, the tugging of the moon’s gravity and tidal forces on the Earth, acing like a brake on the rotation of the planet.

Now the moon is farther away, and is continuing to move away even farther, however the effect of the moon is still felt on Earth, with a consequence that Earth’s day is still slowing down, albeit minutely.

With modern atomic clocks, it is now possible to account for this slowing and the global timescale used by most technologies to ensure time synchronisation, UTC (Coordinated Universal Time), has to account for this gradual slowing, otherwise, because of the extreme accuracy of atomic clocks, eventually day would slip into night as the Earth slowed and we didn’t adjust our clocks.

Because of this, once or twice a year, an extra second is added to the global timescale. These leap-seconds, as they are known, have been added since the 1970’s when UTC was first developed.

For many modern technologies where millisecond accuracy is required, this can cause problems. Fortunately, with NTP time servers (Network Time Protocol) these leap seconds are accounted for automatically, so any technologies hooked up to an NTP server need not worry about this discrepancy.

NTP servers are used by time sensitive technology and computer networks worldwide to ensure precise and accurate time, all the time, regardless of what the heavenly bodies are doing.

Press Release: Galleon Systems Launch New Website

  |   By

Atomic clock and NTP server specialists, Galleon Systems, have relaunched their website providing an improved platform to showcase their wide range of time synchronisation and network time server products.

Galleon Systems, who have been providing atomic clock and time server products to industry and commerce for over a decade, have redesigned their website to ensure the company continues to be world leaders in providing accurate, secure and reliable time synchronisation products.

With detailed descriptions of their product range, new product pictures and a revamped menu system to provided better functionality and user experience, the new website includes all of Galleons extensive range of NTP server systems (Network Time Protocol) and atomic clock synchronisation products.

Time servers from Galleon Systems are accurate to within a fraction of a second and are a secure and reliable method of getting a source of atomic clock time for computer networks and technological applications.

Using either GPS or the UKs MSF radio signal (DSF in Europe WWVB in the USA), time servers from Galleon Systems can keep hundreds of devices on a network accurate to within a few milliseconds of the international timescale UTC (Coordinated Universal Time).

Galleon Systems product range includes a variety of NTP time servers that can receive either GPS or radio referenced signals, dual systems that can receive both, simple radio controlled atomic clock servers, and a range of large network digital and analogue wall clocks.

Manufactured in the UK, Galleon Systems have a wide range of NTP and time synchronisation devices used worldwide by thousands of organizations who need accurate, reliable and precise time. For more information please visit their new website: www.galsys.co.uk

Mechanisms of Time History of Chronological Devices

  |   By

Nearly every device seems to have a clock attached to it these days. Computers, mobile phones and all the other gadgets we use are all good sources of time. Ensuring that no matter where you are a clock is never that far away – but it wasn’t always this way.

Clock making, in Europe, started around the fourteenth century when the first simple mechanical clocks were developed. These early devices were not very accurate, losing perhaps up to half an hour a day, but with the development of pendulums these devices became increasingly more accurate.

However, the first mechanic al clocks were not the first mechanical devices that could tell and predict time. Indeed, it seems Europeans were over fifteen hundred years late with their development of gears, cogs and mechanical clocks, as the ancients had long ago got there first.

Early in the twentieth century a brass machine was discovered in a shipwreck (Antikythera wreck) off Greece, which was a device as complex as any clock made in Europe up in the mediaeval period. While the Antikythera mechanism is not strictly a clock – it was designed to predict the orbit of planets and seasons, solar eclipses and even the ancient Olympic Games – but is just as precise and complicated as Swiss clocks manufactured in Europe in the nineteenth century.

While Europeans had to relearn the manufacture of such precise machines, clock making has moved on dramatically since then. In the last hundred or so years we have seen the emergence of electronic clocks, using crystals such as quartz to keep time, to the emergence of atomic clocks that use the resonance of atoms.

Atomic clocks are so accurate they won’t drift by even a second in a hundred thousand years which is phenomenal when you consider that even quartz digital clocks will drift several seconds n a day.

While few people will have ever seen an atomic clock as they are bulky and complicated devices that require teams of people to keep them operational, they still govern our lives.

Much of the technologies we are familiar with such as the internet and mobile phone networks, are all governed by atomic clocks. NTP time servers (Network Time Protocol) are used to receive atomic clock signals often broadcast by large physics laboratories or from the GPS (Global Positioning System) satellite signals.

NTP servers then distribute the time around a computer network adjusting the system clocks on individual machines to ensure they are accurate. Typically, a network of hundreds and even thousands of machines can be kept synchronised together to an atomic clock time source using a single NTP time server, and keep them accurate to within a few milliseconds of each other (few thousandths of a second).

How Atomic Clocks Control our Transport Systems

  |   By

Getting from A to B has been a primary concern for societies ever since the first roads were built. Whether it is horseback, carriage, train, car or plane – transportation is what enables societies to grow, prosper and trade.

In today’s world, our transportation systems are highly complex due to the sheer numbers of people who are all trying to get somewhere – often at similar times such as rush hour. Keeping the motorways, highways and railways running, requires some sophisticated technology.

Traffic lights, speed cameras, electronic warning signs, and railway signals and point systems have to be synchronised for safety and efficiency. Any differences in time between traffic signals, for instance, could lead to traffic queues behind certain lights, and other roads remaining empty. While on the railways, if points systems are being controlled by an inaccurate clock, when the trains arrive the system may be unprepared or not have switched the line – leading to catastrophe.

Because of the need for secure, accurate and reliable time synchronisation on our transport systems, the technology that controls them is often synchronised to UTC using atomic clock time servers.

Most time servers that control such systems have to be secure so they make use of Network Time Protocol (NTP) and receive a secure time transmission either utilising atomic clocks on the GPS satellites (Global Positioning System) or by receiving a radio transmission from a physics laboratory such as NPL (National Physical Laboratory) or NIST (National Institute of Standards and Time).

In doing so, all traffic and rail management systems that operate on the same network are accurate to each other to within a few milliseconds of this atomic clock generated time and the NTP time servers that keep them synchronised ensures they stay that way, making minute adjustments to each system clock to cope with the drift.

NTP servers are also used by computer networks to ensure that all machines are synced together. By using a NTP time server on a network, it reduces the probability of errors and ensures the system is kept secure.

UTC One Time to Rule Them All

  |   By

In a global economy time has become a more crucial than ever before. As people across the globe, communicate, conference and buy and sell from each other, being aware of the each other’s time is vital for conducting business successfully.

And with the internet, global communication and time awareness are even more important as computers require a source of time for nearly all their applications and processes. The difficulty with computer communication, however, is that if different machines are running different times, all sorts of errors can occur. Data can get lost, errors fail to log; the system can become unsecure, unstable and unreliable.

Time synchronisation for computer networks communicating with each other is, therefore, essential – but how is it achieved when different networks are in different time-zones?

The answer lies with Universal Coordinated Time (UTC) an international time-zones developed in the 1970’2 that is based on accurate atomic clocks.  UTC is set the same the world over, with no accounting for time-zones so the time on a network in the UK – will be identical to the network time in the USA.

UTC time on a computer network is also kept synchronised through the use of NTP (Network Time Protocol) and an NTP server.  NTP ensures all devices on a networked system have exactly the right time as different computer clocks will drift at varying rates – even if the machines are identical.

While UTC makes no accounting for time-zones system clocks can still be set to the local time-zone but the applications and functions of a computer will use UTC.

UTC time is delivered to computer networks through a variety of sources: radio signals, the GPS signal, or across the internet (although the accuracy of internet time is debatable). Most computer networks have a NTP time server somewhere in their server room which will receive the time signal and distribute it through the network ensuring all machines are within a few milliseconds of UTC and that the time on your network corresponds to every other UTC network on the globe.

Origin of Synchronisation (Part 2)

  |   By

Continued…

Most towns and cities would have a main clock, such as Big Ben in London, and for those living near-by, it was fairly easy to look out the window and adjust the office or factory clock to ensure synchronicity; however, for those not in view of these tower clocks, other systems were used.

Commonly, somebody with a pocket watch would set the time by the tower clock in the morning and then go around businesses and for a small fee, let people know exactly what the time was, thus enabling them to adjust the office or factory clock to suit.

When, however, the railways began, and timetables became important it was clear a more accurate method of time keeping was needed, and it was then that the first official time-scale was developed.

As clocks were still mechanical, and therefore inaccurate and prone to drift, society again turned to that more accurate chronometer, the sun.

It was decided that when the sun was directly above a certain location, that would signal noon on this new time-scale. The location: Greenwich, in London, and the time-scale, originally called railway time, eventually became Greenwich Meantime (GMT), a time-scale that was used until the 1970’s.

Now of course, with atomic clocks, time is based on an international time-scale UTC (Coordinated Universal Time) although its origins are still based on GMT and often UTC is still referred to as GMT.

Now with the advent of international trade and global computer networks, UTC is used as the basis of nearly all international time. Computer networks deploy NTP servers to ensure that the time on their networks are accurate, often to a thousandth of a second to UTC, which means all around the world computers are ticking with the same accurate time – whether it is in London, Paris, or New York, UTC is used to ensure that computers everywhere can accurately communicate with each other, preventing the errors that poor time synchronisation can cause.

Origin of Synchronisation (Part 1)

  |   By

Part One

With modern NTP servers (Network Time Protocol) synchronisation is made easy. By receiving a signals from GPS or radio signals such as MSF or WWVB, computer networks consisting of hundreds of machines can easily be synchronised together, ensuring trouble free networking and accurate time-stamping.

Modern NTP time servers are reliant on atomic clocks, accurate to billions of parts of a second, but atomic clocks have only been around for the last sixty years and synchronisation has not always been so easy.

In the early days of chronology, clocks mechanical in nature, were not very accurate at all. The first time-pieces could drift by up to an hour a day so the time could differ from town clock to town clock, and most people in the agricultural based society regarded them as a novelty, relying in stead on sunrise and sunset to plan their days.

However, following the industrial revolution, commerce became more important to society and civilisation, and with it, the need to know what the time was; people needed to know when to go to work, when to leave and with the advent of railways, accurate time became even more crucial.

In the early days if industry, workers were often woken for work by people paid to wake them up. Known as ‛knocker-uppers.’ Relying on the factory time-peice, they would go around town and tap on people’s windows, alerting them to the start of the day, and the factory hooters signalled the beginning and end of shifts.

However, as commerce developed time became even more crucial, but as it would take another century or so for more accurate timepieces to develop (until at least the invention of electronic clocks), other methods were developed.

To follow…

Finding an Online NTP Time Source

  |   By

Finding a source of time to synchronise a computer network to can be a challenge as there are a myriad of online time sources, all pertaining to be accurate and reliable; however, the truth can be rather different with many online sources either in too much demand, too far away or inaccurate.

NTP (Network Time Protocol) requires a source of UTC time (Coordinated Universal Time) which is kept true by atomic clocks. Online time sources are not themselves atomic clocks but NTP server devices that receive the time from an atomic clock which is then relayed to the devices that connect to the online time server.

There are two types of online time server: stratum 1 devices – devices that receive the time directly from an atomic clock, either using GPS or a radio reference signal. Stratum 2 devices  on the other hand are one step further away in that they are receive their time from a stratum 1 time server.

Because of demand, finding an online stratum 1 time server is next to impossible, and those that do take request usually do so under a subscription, which leaves the only choice for most people being a stratum 2 device.

There are plenty of resources on the internet that provide locations for online time servers.

But there are drawbacks to using such devices; firstly, online stratum 2 time sources can’t be guaranteed and several surveys taken have found that the reliability and accuracy of many of them can’t be taken for granted.  Secondly, online sources of time require an open firewall port which can be manipulated by malicious bots or users – leading to security risks.

A far better solution for most networks is to install your own stratum 1 NTP server. These time server devices sync to atomic clocks outside the firewall (using GPS or radio signals) and therefore are not security risks. They are also accurate to a few milliseconds ensuring the network will always be accurate to UTC.

Do I Really Need an NTP Time Server?

  |   By

NTP (Network Time Protocol) is one of the oldest protocols still in use today. It was developed in the 1980’s when the internet was still in its infancy and was designed to help computers synchronise together, preventing drift and ensuring devices can communicate with unreliable time causing errors.

NTP is now packaged in most operating systems and forms the basis for time synchronisation in computers, networks and other technologies. Most technologies and networks use a network time server (commonly called an NTP time server) for this task.

These time servers are external devices that receive the time from a radio frequency or GPS signal (both generated by atomic clocks). This time signal is then distributed across the network using NTP ensuring all devices are using the exact same time.

As NTP is ubiquitous in most operating systems and the internet is awash with sources of atomic clock time, this begs the question of whether NTP time servers are still necessary for modern computer networks and technology.

There are two reasons why networks should always use a NTP time server and not rely on the internet as a source of time for synchronisation. Firstly, internet time can never be guaranteed. Even if the source of time is 100% accurate and kept true (incidentally most sources of internet time are derived using an NTP time server at the host’s end) the distance from the host can lead to discrepancies.

Secondly, and perhaps fundamentally more important to most business networks is security. NTP time servers work externally to the network. The source of time either radio of GPS, is secure, accurate and reliable and as it is external to the network it can’t be tampered with en-route, or used to disguise malicious software and bots.

NTP servers don’t require an open port in the firewall, unlike internet sources of time which can be used as an entry point by malicious users and software.