Re: Network desintegrating(?)

Dieter Visser wrote:
Hello,

Thanks for your answer. I put the files you asked for as a
attachment. I've seen that before but don't know what to do about it.
I know PDC and BDC are NT 4 terms, TELSERV is the SBS box, NOODSERV
is the extra DC.

Thanks for your time.
Dieter

Two things. One, you should ony use static IP addresses for servers and
especially domain controllers. OK, three things. After replication is fixed
change the DHCP scope to give clients both DCs as DNS servers.

Disable the windows firewall on NOODServ (probably what is causing the
connectivity issues). Is this Premium with ISA or just dual nic SBS
standard?

--------

Windows IP Configuration



Host Name . . . . . . . . . . . . : noodserv

Primary Dns Suffix . . . . . . . : bsd.local

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : bsd.local



Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . : bsd.local

Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network
Connection

Physical Address. . . . . . . . . : 00-13-20-4F-79-0D

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 10.10.10.22

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 10.10.10.2

DHCP Server . . . . . . . . . . . : 10.10.10.2

DNS Servers . . . . . . . . . . . : 10.10.10.2

Primary WINS Server . . . . . . . : 10.10.10.2

Lease Obtained. . . . . . . . . . : vrijdag 25 januari 2008 9:17:46

Lease Expires . . . . . . . . . . : zaterdag 2 februari 2008 9:17:46
---------
Testing server: Default-First-Site-Name\TELSERV
Starting test: Connectivity
Server TELSERV resolved to this IP address 10.10.10.2,
but the address couldn't be reached(pinged), so check the network.
The error returned was: Error due to lack of resources.
This error more often means that the targeted server is
shutdown or disconnected from the network
......................... TELSERV failed test Connectivity
---------

"kj [SBS MVP]" <KevinJ.SBS@xxxxxxxxxxxxxxxxxx> wrote in message
news:%23MW$R7sXIHA.1208@xxxxxxxxxxxxxxxxxxxxxxx
Dieter Visser wrote:
Hello,

1 SBS 2003 SP1 server, 1 Windows 2003 member server as a BDC, 15
clients XP Pro SP2

For some reason I get on the BDC event 13508 errors:

The File Replication Service is having trouble enabling replication
from TELSERV to NOODSERV for c:\windows\sysvol\domain using the DNS
name telserv.bsd.local. FRS will keep retrying.
Following are some of the reasons you would see this warning.


[1] FRS can not correctly resolve the DNS name telserv.bsd.local
from this computer.

[2] FRS is not running on telserv.bsd.local.

[3] The topology information in the Active Directory for this
replica has not yet replicated to all the Domain Controllers.


This event log message will appear once per connection, After the
problem is fixed you will see another event log message indicating
that the connection has been established.

Telserv is the PDC, Noodserv is the BDC. I can ping from the PDC to
the BDC, I can ping all the clients. Everything works fine so far I
can see.
From the BDC I can't ping the PDC. All other connections work oke.

AFAIK dhcp and dns work oke, there are no events in the logs.

On a couple of clients are Userenv errors. Are they related maybe?

The Ipconfig of the PDC and the BDC are attached.

Any help is very welcom, thanks in advance for your time

Dieter

Setting aside the PDC/BDC terminology (for now), it's likely the
Second DC ("BDC") has DNS issues with the First DC ("PDC").

post the output of ipconfig/all from both of your DCs'

Alternativly, run dcdiag /c /e on both and post the complete results.


--
/kj

--
/kj


.

Relevant Pages

  • Re: STATUS_OPLOCK_NOT_GRANTED
    ... tested FRS replication and it worked. ... >>Integrated DNS, ... >>>>> see another event log message indicating that the ... >>>>> connection has been established. ...
    (microsoft.public.windows.server.active_directory)
  • Re: W2K3 Server Logon Script Question...
    ... This can take some time for replication parts. ... in the DNS server list of the NIC from server 2. ... This event log message will appear once per connection, ...
    (microsoft.public.win2000.networking)
  • Re: SRV records
    ... Ethernet adapter Local Area Connection: ... The attempt to establish a replication link for the following writable ... Source domain controller address: ... 8524 The DSA operation is unable to proceed because of a DNS lookup failure. ...
    (microsoft.public.windows.server.dns)
  • Re: W2K3 Server Logon Script Question...
    ... Windows IP Configuration ... Ethernet adapter Local Area Connection: ... Connection-specific DNS Suffix. ... The File Replication Service is having trouble enabling replication ...
    (microsoft.public.win2000.networking)
  • Re: Network desintegrating(?)
    ... I know PDC and BDC are NT 4 terms, TELSERV is the SBS box, NOODSERV ... fixed change the DHCP scope to give clients both DCs as DNS servers. ... Ethernet adapter Local Area Connection: ...
    (microsoft.public.windows.server.sbs)
Loading