Hello,
I just get a server with CentOS 6.4, I have install Webmin and
Vitualmin running OK, but I can't run correctly DNS server.
I set hostname: dns.maca.li
Resolution order: Host file, DNS
DNS servers: 127.0.0.1 and 91.121.137.55
Search Domain: maca.li
When I creta virtual server with
It's just saying the records don't match from your parent nameserver.
[root@janus ~]# dig ns maca.li +trace
; DiG 9.3.6-P1-RedHat-9.3.6-20.P1.el5 ns maca.li +trace
;; global options: printcmd
. 3600IN NS i.root-servers.net.
. 3600IN
Hi,
Actually, the website is found, but when I create new virtual servers
withs virutalmin, noone can be access.
I have already try
ns.maca.li. IN A 91.121.137.55
NS INNSmaca.li.
But it do nothing,
Thanks,
Ernesto
Quoting Banyan He ban...@rootong.com:
Hi
what do they access to? How to access? How's the verification being
handled here?
Maybe a capture on port 53 explains everything.
Banyan He
Blog: http://www.rootong.com
Email: ban...@rootong.com
On 3/19/2013 1:15 AM, Weplica wrote:
Hi,
Actually, the website is found, but when I
I am not using Samba 3.x. I am using Samba3x-3.3.8. As I understand it,
RHEL provided this branch so that Windows 7 could join a Samba domain.
That aside, It does not seems to me that the error message indicates that
it cannot resolve where the PDC is. What method is Windows 7 trying to use
On Thu, 2010-07-08 at 08:13 -0500, Doug Coats wrote:
I am not using Samba 3.x. I am using Samba3x-3.3.8. As I understand
it, RHEL provided this branch so that Windows 7 could join a Samba
domain.
That aside, It does not seems to me that the error message indicates
that it cannot resolve
I think as long as persist in chasing pointless ends, you will continue
to fail.
DNS AD are not at issue here. Samba 3 cannot provide AD services.
If resolution is a problem, it may be that you don't have nmb running on
your Samba server and you probably want it to be a wins server if it
On Thu, 2010-07-08 at 10:34 -0500, Doug Coats wrote:
I think as long as persist in chasing pointless ends, you will
continue
to fail.
DNS AD are not at issue here. Samba 3 cannot provide AD
services.
If resolution
I think you are being vague (similar error).
What is the exact error?
What is the output of 'testparm -sv' ?
Craig
Sorry for being to vague.
Here is the XP Pro error I get when I try to join the domain.
A domian controller for the domain admin could not be contacted.
Esure that the
Sorry for being to vague.
Here is the XP Pro error I get when I try to join the domain.
A domian controller for the domain admin could not be contacted.
Esure that the domain name is typed correctly.
If the name is correct, click on the Details for troubleshooting
information.
Details:
On Thu, 2010-07-08 at 12:03 -0500, Doug Coats wrote:
I think you are being vague (similar error).
What is the exact error?
What is the output of 'testparm -sv' ?
Craig
Sorry for being to vague.
Here is the
On 07/08/2010 05:34 PM, Doug Coats wrote:
...
Has anyone been able to get Samba3x.3.3.8 to work as a PDC?
It worked for me in a test setup I had a month ago:
Made a copy of our main CentOS 5 server, replace samba with samba3x,
and I was able to join XP and W7 (with registry patch) to the
On Thu, 2010-07-08 at 12:03 -0500, Doug Coats wrote:
Here is the testparm -sv you requested.
For a short explaination of the IP's listed. We have two domains.
One served by 192.168.6.1 and one by 192.168.5.1. I am currantly
upgrading the 192.168.6. network to Windows 7. Or atleast
On Thu, 2010-07-08 at 13:44 -0400, JohnS wrote:
On Thu, 2010-07-08 at 12:03 -0500, Doug Coats wrote:
Here is the testparm -sv you requested.
For a short explaination of the IP's listed. We have two domains.
One served by 192.168.6.1 and one by 192.168.5.1. I am currantly
His problem is WINS resolution doesn't tell the workstations which
computer is the domain controller and that is what he needs to fix
(first by designating a domain controller and then by making sure that
WINS is functioning well).
Craig
Thanks for all the help. I agree that WINS seems
On Thu, 2010-07-08 at 10:50 -0700, Craig White wrote:
On Thu, 2010-07-08 at 13:44 -0400, JohnS wrote:
On Thu, 2010-07-08 at 12:03 -0500, Doug Coats wrote:
Here is the testparm -sv you requested.
For a short explaination of the IP's listed. We have two domains.
One served
On Thu, 2010-07-08 at 12:58 -0500, Doug Coats wrote:
His problem is WINS resolution doesn't tell the workstations
which
computer is the domain controller and that is what he needs to
fix
(first by designating a domain controller and then by
a 'network' is 192.168.x assuming that you are using class C subnet
masks (255.255.255.0) and so you should have a WINS server on EACH
network (192.168.4, 192.168.5, 192.168.6, etc.)
Cross network browsing is somewhat of a hit or miss and not reliable...
for a number of reasons such as the
On 7/8/2010 1:15 PM, Craig White wrote:
a 'network' is 192.168.x assuming that you are using class C subnet
masks (255.255.255.0) and so you should have a WINS server on EACH
network (192.168.4, 192.168.5, 192.168.6, etc.)
I thought the point of WINS was to have a single address that would
I do think that I have hit upon an issue. The WINS data for samba is kept
in /var/cache/samba.dat but it is updated dynamically with nmdb. It has
dated data. When I moved the server I changed the server name slightly and
so the WINS data points to the old name at the current IP. In fact
Doug Coats wrote:
I do think that I have hit upon an issue. The WINS data for samba is
kept in /var/cache/samba.dat but it is updated dynamically with nmdb.
It has
dated data. When I moved the server I changed the server name slightly
and so the WINS data points to the old name at the
With the WINS data cleared. for the past 20 min. (I did it before I wrote
about it) Neither PDC has reported to WINS. So no wonder my PC's can't find
their domain.
So how do I make sure that 192.168.6.1 is added to wins.dat. I could do it
manually but I would rather it communicate the way that
On Thu, 2010-07-08 at 13:41 -0500, Doug Coats wrote:
I agree that preferred master should have been set to yes. I made
that change with but still no joy.
I don't mean to be contrary but our cross subnet browsing has been
working since 2003 when we set up this network. It has been very
Um, does a timing issue come into play here? If the local clock is not
within a few seconds, we can't connect to AD (we are going through
kerborous). Is there time data in the cache?
mark
Both the XP box and the Windows 7 use the PDC server as their time server so
they are set to
---
Ok since you say the interdomain networking is functioning (triangle
routing) have a read at this:
http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/domain-member.html#id2573732
John
all else that fails put that machine on another known working Subnet and
have a go at that.
On Thu, 2010-07-08 at 13:43 -0500, Les Mikesell wrote:
On 7/8/2010 1:15 PM, Craig White wrote:
a 'network' is 192.168.x assuming that you are using class C subnet
masks (255.255.255.0) and so you should have a WINS server on EACH
network (192.168.4, 192.168.5, 192.168.6, etc.)
I
On 7/8/2010 1:52 PM, Doug Coats wrote:
With the WINS data cleared. for the past 20 min. (I did it before I
wrote about it) Neither PDC has reported to WINS. So no wonder my PC's
can't find their domain.
So how do I make sure that 192.168.6.1 is added to wins.dat. I could do
it manually but
On Thu, 2010-07-08 at 13:52 -0500, Doug Coats wrote:
With the WINS data cleared. for the past 20 min. (I did it before I
wrote about it) Neither PDC has reported to WINS. So no wonder my
PC's can't find their domain.
So how do I make sure that 192.168.6.1 is added to wins.dat. I could
On 7/8/2010 2:12 PM, Craig White wrote:
I thought the point of WINS was to have a single address that would
collate the names/addresses from all your networks.
The important thing is to get the WINS working on EACH network. It's
also easiest to have your PDC be the WINS server - period.
I just did a checkconfig on the PDC in question 192.168.6.1. And I noticed
something that might be nothing but it puzzles me. The nmb service is set
to off at all run levels. If I check the nmb status it says that it is
stopped. Doesn't Samba need that for net-bios support? I am probably
On Thu, 2010-07-08 at 14:12 -0500, Doug Coats wrote:
As I said in another post I changed the machine name to an entirely
different format and I didn't copy any domain information from the
prior machine(meaning I didn't try to migrate the information placed
in the smbpasswd). Since all the
On Thu, 2010-07-08 at 14:29 -0500, Les Mikesell wrote:
WINS is a broadcast based protocol and thus it only works on the local
network and each subnet/network MUST necessarily have master browser
elections. The WINS server on each subnet would serve as a clearing
house for name resolution
On Thu, 2010-07-08 at 14:36 -0500, Doug Coats wrote:
I just did a checkconfig on the PDC in question 192.168.6.1. And I
noticed something that might be nothing but it puzzles me. The nmb
service is set to off at all run levels. If I check the nmb status
it says that it is stopped. Doesn't
On Thu, 2010-07-08 at 14:36 -0500, Doug Coats wrote:
I just did a checkconfig on the PDC in question 192.168.6.1. And I
noticed something that might be nothing but it puzzles me. The nmb
service is set to off at all run levels. If I check the nmb status
it says that it is stopped. Doesn't
Doug Coats wrote:
mark wrote:
Um, does a timing issue come into play here? If the local clock is not
within a few seconds, we can't connect to AD (we are going through
kerborous). Is there time data in the cache?
Both the XP box and the Windows 7 use the PDC server as their time server
so
On 7/8/2010 2:36 PM, Doug Coats wrote:
I just did a checkconfig on the PDC in question 192.168.6.1. And I
noticed something that might be nothing but it puzzles me. The nmb
service is set to off at all run levels. If I check the nmb status it
says that it is stopped. Doesn't Samba need
How 'bout with the server that's supposed to be the master, above the two
other PDCs?
mark
It is set up to NTP to the same external servers so they should all be in
sync.
___
CentOS mailing list
CentOS@centos.org
On Thu, 2010-07-08 at 14:29 -0500, Les Mikesell wrote:
On 7/8/2010 2:12 PM, Craig White wrote:
I thought the point of WINS was to have a single address that would
collate the names/addresses from all your networks.
The important thing is to get the WINS working on EACH network. It's
On 7/8/2010 2:43 PM, JohnS wrote:
WINS is a broadcast based protocol and thus it only works on the local
network and each subnet/network MUST necessarily have master browser
elections. The WINS server on each subnet would serve as a clearing
house for name resolution for each subnet/network.
Netbios can use multiple network transports, some of which only have
broadcasts to support name resolution. Each subnet will elect a master
browser to collect the names and respond to queries. As an extension
for the IP protocol which is routeable, the WINS service accepts the
lists from
On Thu, 2010-07-08 at 14:55 -0500, Les Mikesell wrote:
Correct and Not Correct... How about that? There really is no right or
wrong in either of you twos answer. The right way is Wins on every SN
to pass to the MB. That's my opinion.
So what do you do on a VPN connection that is
On 7/8/2010 3:11 PM, JohnS wrote:
On Thu, 2010-07-08 at 14:55 -0500, Les Mikesell wrote:
Correct and Not Correct... How about that? There really is no right or
wrong in either of you twos answer. The right way is Wins on every SN
to pass to the MB. That's my opinion.
So what do you do
On Thu, 2010-07-08 at 15:31 -0500, Les Mikesell wrote:
And your getting at what? How does this relate to the OPs problem?
I'm getting at your assertion that a Wins server on every subnet is
right being impractical in most networks. And like the OPs problem
it has to do with a windows
On 7/8/2010 4:00 PM, JohnS wrote:
Windows name resolution has next to nothing to do with ip routing. If
your routing works you can make windows name resolution work over it,
but it isn't automatic.
If it does not work then it want happen as in getting routed to the
wins server. You
After a little bit of research I feel a little vindicated. It seems that
Samba3x seporated out nmb. On Samba 3.0 the nmb service does not show up in
the chkconfig. It simply starts and stops with smb.
On Samba3x it seporates out nmb and it does not start by itself. So based
on my experience I
On Thu, 2010-07-08 at 18:10 -0500, Doug Coats wrote:
After a little bit of research I feel a little vindicated. It seems
that Samba3x seporated out nmb. On Samba 3.0 the nmb service does not
show up in the chkconfig. It simply starts and stops with smb.
On Samba3x it seporates out nmb
On 07/08/10 1:31 PM, Les Mikesell wrote:
I'm getting at your assertion that a Wins server on every subnet is
right being impractical in most networks. And like the OPs problem
it has to do with a windows client being able to resolve a windows name
on a different subnet.
I've never
On Thu, 2010-07-08 at 17:07 -0700, John R Pierce wrote:
On 07/08/10 1:31 PM, Les Mikesell wrote:
I'm getting at your assertion that a Wins server on every subnet is
right being impractical in most networks. And like the OPs problem
it has to do with a windows client being able to resolve
I am running centos 5.5 using samba3x as a pdc. I migrated to samba3x so
that I could join Windows 7 machines to the domain. It is a new setup using
a tried and true configuration from a different box. I have used this
configuration in the past to joing Windows XP Pro machines. And I havn't
On Wed, 2010-07-07 at 20:40 -0500, Doug Coats wrote:
I am running centos 5.5 using samba3x as a pdc. I migrated to samba3x
so that I could join Windows 7 machines to the domain. It is a new
setup using a tried and true configuration from a different box. I
have used this configuration in
: Les Mikesell [EMAIL PROTECTED]Assunto: Re: [CentOS] DNS problem (on NAT configuration)Para:
"CentOS mailing list" centos@centos.orgCc: [EMAIL PROTECTED]Data: Quinta-feira, 24 de Abril de 2008, 18:56Patricia Bittencourt wrote: Hi, I'm dealing with a problem that the wo
Patricia Bittencourt wrote:
Thank you Les, John, for the reply.
One thing that I noticed is that there are lots of nfs connections in
TIME_WAIT. And since I have been facing problems with NFS (ie. taking
too much time to cd to a mounting area on client) the problems regarding
network
On Thu, 2008-04-24 at 14:27 -0700, Patricia Bittencourt wrote:
Hi,
I'm dealing with a problem that the worker nodes that are
behind a NAT aren't able to reach outside from time to time. (ie: on a
given moment I can ping an address name and immediately after I
cannot: ping:
53 matches
Mail list logo
