Re: Network desintegrating(?)

Hello,

For what its worth. A different answer on Telserv and Noodserv after
REPADMIN /SHOWREPS

Default-First-Site-Name\NOODSERV
DC Options: IS_GC
Site Options: (none)
DC object GUID: 8ebd0137-ec8f-4441-b813-ab4bea89d449
DC invocationID: e0d43f1f-fdd4-40f3-ba4f-d19c11f581f4

==== INBOUND NEIGHBORS ======================================

DC=bsd,DC=local
Default-First-Site-Name\TELSERV via RPC
DC object GUID: d784de39-d662-4215-aeb8-a5d3c580ddea
Last attempt @ 2008-01-30 12:48:15 failed, result 1726 (0x6be):
The remote procedure call failed.
988 consecutive failure(s).
Last success @ 2008-01-09 10:09:42.

CN=Configuration,DC=bsd,DC=local
Default-First-Site-Name\TELSERV via RPC
DC object GUID: d784de39-d662-4215-aeb8-a5d3c580ddea
Last attempt @ 2008-01-30 12:48:14 failed, result 1726 (0x6be):
The remote procedure call failed.
658 consecutive failure(s).
Last success @ 2008-01-09 09:50:14.

CN=Schema,CN=Configuration,DC=bsd,DC=local
Default-First-Site-Name\TELSERV via RPC
DC object GUID: d784de39-d662-4215-aeb8-a5d3c580ddea
Last attempt @ 2008-01-30 12:48:14 failed, result 1726 (0x6be):
The remote procedure call failed.
501 consecutive failure(s).
Last success @ 2008-01-09 09:50:14.

Source: Default-First-Site-Name\TELSERV
******* 988 CONSECUTIVE FAILURES since 2008-01-09 10:09:42
Last error: 1726 (0x6be):
The remote procedure call failed.

Default-First-Site-Name\TELSERV
DC Options: IS_GC
Site Options: (none)
DC object GUID: d784de39-d662-4215-aeb8-a5d3c580ddea
DC invocationID: d784de39-d662-4215-aeb8-a5d3c580ddea

==== INBOUND NEIGHBORS ======================================

DC=bsd,DC=local
Default-First-Site-Name\NOODSERV via RPC
DC object GUID: 8ebd0137-ec8f-4441-b813-ab4bea89d449
Last attempt @ 2008-01-30 12:47:19 was successful.

CN=Configuration,DC=bsd,DC=local
Default-First-Site-Name\NOODSERV via RPC
DC object GUID: 8ebd0137-ec8f-4441-b813-ab4bea89d449
Last attempt @ 2008-01-30 12:47:19 was successful.

CN=Schema,CN=Configuration,DC=bsd,DC=local
Default-First-Site-Name\NOODSERV via RPC
DC object GUID: 8ebd0137-ec8f-4441-b813-ab4bea89d449
Last attempt @ 2008-01-30 12:47:19 was successful.


"Dieter Visser" <kdv@xxxxxxxxx> wrote in message
news:%235mnuqxYIHA.2268@xxxxxxxxxxxxxxxxxxxxxxx
Hello,

I just noticed that the group policy is not updated after a GPUPDATE
/FORCE. So the network is desintegrating after all.

This is getting serious then.

Regards
Dieter


"Dieter Visser" <kdv@xxxxxxxxx> wrote in message
news:uuwlS8wYIHA.5028@xxxxxxxxxxxxxxxxxxxxxxx
Hello,

I can't ping Telserv from the clients or Noodserv. The other way around
works, all the clients and Telserv can ping Noodserv.
All programs are working like they should. We have one Foxpro
server/client program running on all the clients where the data is stored
on the SBS box. Network traffic is not heavy. Just a few Office users
writing letters.

Is this cable trouble or something with ISA?

Thanks for your patience.

Regards
Dieter


"kj [SBS MVP]" <KevinJ.SBS@xxxxxxxxxxxxxxxxxx> wrote in message
news:ukUVHZpYIHA.4440@xxxxxxxxxxxxxxxxxxxxxxx
Dieter Visser wrote:
Hello kj,

Thanks for your answer. SuperGumby answered as well.

1 SBS 2003 SP1 server Premium with ISA 2004, 1 Windows 2003 as DC, 15
clients XP Pro SP2

Physically it's
Internet

DSL modem (yes it's a speedtouch)

SBS External
SBS Internal

Internal switch

Lan PC's

I made a reservation for Noodserv in DHCP. I will enter Noodserv as
extra DNS server.
I don't understand the firewall issue. The system was working from
2005 till recently with the firewall client installed. I'm not
questioning you advice, I' m trying to learn something.

The results of the test you performed indicate network connectivity
problems between the two DC with even simple pings failing to TELSERV.
On a simple flat network this usually is a Internal configuration
problem with the server (TELSERV) if not an obvious cabling one. If the
windows 2003 firewall is "on" and using the default blocks, these same
symptoms are frequently seen.

Can you successfully ping TELSERV from the XP clients, but not from the
NOODSERV?

Server TELSERV resolved to this IP address 10.10.10.2,
but the address couldn't be reached(pinged), so check the
network.




"kj [SBS MVP]" <KevinJ.SBS@xxxxxxxxxxxxxxxxxx> wrote in message
news:%23su778cYIHA.4696@xxxxxxxxxxxxxxxxxxxxxxx
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

--
/kj







.

Relevant Pages

  • Re: Network desintegrating(?)
    ... All symptoms of network connectivity problems. ... I can't ping Telserv from the clients or Noodserv. ...
    (microsoft.public.windows.server.sbs)
  • Re: Network desintegrating(?)
    ... I can't ping Telserv from the clients or Noodserv. ...
    (microsoft.public.windows.server.sbs)
  • Re: Network desintegrating(?)
    ... So the network is desintegrating after all. ... I can't ping Telserv from the clients or Noodserv. ...
    (microsoft.public.windows.server.sbs)
  • Re: Network desintegrating(?)
    ... I made a reservation for Noodserv in DHCP. ... The results of the test you performed indicate network connectivity problems ... between the two DC with even simple pings failing to TELSERV. ... Can you successfully ping TELSERV from the XP clients, ...
    (microsoft.public.windows.server.sbs)
  • Re: Network desintegrating(?)
    ... 15 clients XP Pro SP2 ... I made a reservation for Noodserv in DHCP. ... I know PDC and BDC are NT 4 terms, TELSERV is the SBS box, NOODSERV ... Ethernet adapter Local Area Connection: ...
    (microsoft.public.windows.server.sbs)
Loading