![]() |
Hello and Welcome from United States to the UNIX and Linux Forums! Thank You for Visiting and Joining Our Global Community.
|
|
google unix.com
|
|||||||
| Forums | Register | Forum Rules | Links | Albums | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| Linux RedHat, Ubuntu, SUSE, Fedora, Debian, Mandriva, Slackware, Gentoo linux, PCLinuxOS. All Linux questions here! |
More UNIX and Linux Forum Topics You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| configuring boot server | kumarmani | SUN Solaris | 9 | 09-30-2009 02:33 PM |
| Client/Server Socket Application - Preventing Client from quitting on server crash | varun.nagpaal | High Level Programming | 2 | 08-27-2009 10:57 PM |
| configuring NIM server | pchangba | AIX | 3 | 06-13-2009 02:05 PM |
| configuring web server | sriram.s | SUN Solaris | 3 | 07-25-2006 08:30 AM |
| configuring same /bash for 4 computer which is thin client | niravuchat | Linux | 0 | 03-11-2004 02:12 AM |
![]() |
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
|
||||
|
configuring an NTP client/server
I need to configure an NTP daemon on a "bridge-PC" connected on 2 LANs. It is expected to read the correct time on a time server on the first LAN and behave as a server for the second LAN.
Can I do both the things with ntpd? In other words, is ntpd able to work as client and server at the same time? I've configured ntp.conf with the external NTP server address on the first LAN, and inserted ./ntdp in the rc.local. The daemon runs correctly, it reads and updates its time, but the other PCs in the second LAN (the "internal"one) do not recognize the "bridge-PC" as an NTP server (even if they are able to ping it). What should be going wrong? Thanks, M. |
![]() |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|