Re: DNS Issue(s)



My junk pile has an HP Procurve 12 port switch. A bullet proof switch
that has never burned me. Almost every other product has let me down
at one time or another. I need to swap that switch out which is on
loan at one account. I have had frustrations with a Cisco switch but
limited experience so that data point is not valid.

I did have an account call complaining about speed. This is an account
that calls every one to two years like clockwork. I spent hours
defragging ancient workstations and the server. I ran updates. I
wondered if it was just slow old workstations. I asked to see their
fastest workstation which was a two year old underpowered box. It at
least popped up the message that it was connected at 10mbs. I went to
their network closet and there were 2 network hubs daisy chained. I
told the owner to go to the store and buy a 24 port switch. Any switch
would be better than a 10 hub. He went out that night and got some
sort of 100 switch. I have not heard back in months so I guess it
fixed the problem.

On Wed, 4 Apr 2007 02:16:06 -0700, Dave Tee
<DaveTee@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

Hi Jim, It is actually a hub. It's been there for a little while now and
been pretty reliable. It was just a cheap solution to a small office that
really only, File, print and email. It is a DS116. I am going to drop a 16
port Cisco switch in there without any specific config to see how it goes.
I'll keep you posted.
--
Dave Tee
Tnx for anyones help


"Jim Behning SBS MVP" wrote:

If you are using hubs than that is a sad day. Switches are much
faster. If you are working with Netgear then that is another strike. I
have had bad luck with Netgear. Friends in Australia have had great
luck with Netgear.

You missed my question. Is the server internal nic being reset or the
workstation nic?

When you have an issue have you power cycled your network switch to
see if the problem goes away?

If a workstation cannot see the server then it cannot resolve a dns
querry.

You replaced what nic on what machine with what nic?

http://eventid.net/display.asp?eventid=6702&eventno=294&source=DNS&phase=1

On Tue, 3 Apr 2007 05:32:08 -0700, Dave Tee
<DaveTee@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

Hi Jim,

Sorry, I never fed you enough information. I agree, this looks like a
network issue rather than server. I have replaced NIC and the Netgear hub.
Only 10 users on a 16 port hub. I can find no trend for when this happens.
All I know that is as soon as this happens I get the same error recorded each
time by DNS. When this happens, if I go to the server (2 x nics 1 public 1 x
private) I still have internet access on the server. It's quite odd. Would
the DNS error be generated becasue of a LAN issue or could it be the cause of
the LAN issue? All the clients go which would indicate a card/lan fault to
me. You views are welcome. Regards. Dave
--
Dave Tee
Tnx for anyones help


"Jim Behning SBS MVP" wrote:

Every pc but not the server? What happens when you replaced the
network switch with a new one? What happens when you flip the
disconnect switch on the HVAC? What happens when you turn off all
halogen lights? Sometimes network issues can be poor cabling
improperly installed. Sometime network switches are bad. Sometimes
workstations are infected.

On Tue, 3 Apr 2007 02:40:04 -0700, Dave Tee
<DaveTee@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

My local client PC's keep getting disconnected. If I disbale the LAN card and
re-enable it again they all come back to life without logging them off/on
again. This has been a problem for a while now, without time to resolve it...
Now I have time. Please help! :-)

On inspection of the event viewer all is ok apart from DNS, which reports..

Event Type: Error
Event Source: DNS
Event Category: None
Event ID: 6702
Date: 02/04/2007
Time: 07:51:24
User: N/A
Computer: OFFICE2003
Description:
DNS server has updated its own host (A) records. In order to ensure that
its DS-integrated peer DNS servers are able to replicate with this server, an
attempt was made to update them with the new records through dynamic update.
An error was encountered during this update, the record data is the error
code.

If this DNS server does not have any DS-integrated peers, then this error
should be ignored.

If this DNS server's Active Directory replication partners do not have the
correct IP address(es) for this server, they will be unable to replicate with
it.

To ensure proper replication:
1) Find this server's Active Directory replication partners that run the DNS
server.
2) Open DnsManager and connect in turn to each of the replication partners.
3) On each server, check the host (A record) registration for THIS server.
4) Delete any A records that do NOT correspond to IP addresses of this
server.
5) If there are no A records for this server, add at least one A record
corresponding to an address on this server, that the replication partner can
contact. (In other words, if there multiple IP addresses for this DNS
server, add at least one that is on the same network as the Active Directory
DNS server you are updating.)
6) Note, that is not necessary to update EVERY replication partner. It is
only necessary that the records are fixed up on enough replication partners
so that every server that replicates with this server will receive (through
replication) the new data.

Thank you for your time and help in advance..


.



Relevant Pages

  • Re: DNS Issue(s)
    ... When you have an issue have you power cycled your network switch to ... If a workstation cannot see the server then it cannot resolve a dns ... Find this server's Active Directory replication partners that run the DNS ...
    (microsoft.public.windows.server.sbs)
  • Re: DNS GC entry
    ... Event Source: DNS ... DNS Server has updated its own host records. ... Find this server's ActiveDirectory replication partners that run the DNS ... Are you getting any Event log errors? ...
    (microsoft.public.win2000.dns)
  • Re: Internet Connection Issues, clients...
    ... I've tried repairing the IP, flushing the DNS, stripping all startup items, manually entering the ip address and DNS server address and switched it back to auto since that didn't resolve the issue. ... Router hardware and internal connection tables. ... Not all that likely, but again, reboot the switch. ...
    (microsoft.public.windows.server.sbs)
  • Re: Network is not visible
    ... Updated the dns record for the local nic to 192.168.32.252 ... Restarted the Server and I had the following errors; ... name" on the network but I am sure there is no duplicate names. ... Find this server's Active Directory replication partners that run the DNS ...
    (microsoft.public.windows.server.sbs)
  • RE: Internet for clients
    ... An error occurred during DNS lookup of the manually ... configured peer 'time.windows.com,0x1'. ... DNS server has updated its own host records. ... Find this server's Active Directory replication partners that run the DNS ...
    (microsoft.public.windows.server.sbs)