Re: Network desintegrating(?)

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.

"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



.

Relevant Pages

  • Re: Clients connecting to server
    ... DNS: 192.168.1.64 ... > I also do not know how to set up DHCP on the SBS and have the Clients ... > I get an internet connection on the server, ...
    (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)
  • Re: Network desintegrating(?)
    ... I know PDC and BDC are NT 4 terms, TELSERV is the SBS box, NOODSERV ... Ethernet adapter Local Area Connection: ... Connection-specific DNS Suffix. ... The File Replication Service is having trouble enabling replication ...
    (microsoft.public.windows.server.sbs)
  • Re: Windows clients randomly go offline?
    ... I have found that most of the time the "clients loose connection" complaint ... is because of an improper entry on the client DNS for the secondary. ... they have their ISP's DNS server listed as secondary. ... AD clients must point to DNS servers set up for the AD domain only. ...
    (microsoft.public.windows.server.networking)
  • IE sometimes failes.
    ... The Clients are w2k and XP with IE 5 and some with IE6 ... On the server the gateway is set to our router, and DNS is set to it self. ... Ethernet adapter Local Area Connection: ...
    (microsoft.public.win2000.dns)
Loading