Merv
Mon Sep 29 07:13:27 CDT 2003
Sounds like a DNS problem since you can't get name resolution on the member
server. Check the binding order of your NICs in the SBS (internal should be
listed first).
And here's a Google search for: "NetDDE event id 206"
http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&q=NetDDE+event+id+206&sa=N&tab=wg
--
Merv Porter [SBS MVP]
===================================
"latha" <latha_madhu@yahoo.com> wrote in message
news:OLW7EHmhDHA.3324@TK2MSFTNGP11.phx.gbl...
> OK thanks for your reply. so to solve this problem is it NIC problem or
ant
> other device ?help me
>
>
> thanks and regards
> latha
>
> .
> "Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]" <sbradcpa@pacbell.net>
> wrote in message news:uUn4zflhDHA.2748@TK2MSFTNGP11.phx.gbl...
> > From www.eventid.net
> >
> > Source NetDDE
> > Type Error
> > Description Listen failed: 15:
> > Comments Adrian Grigorof (Last update 7/23/2003):
> > As per Microsoft, the computer was expecting data from another computer
> > but has not received it. Either the other computer is not sending, or
> > the thread on this computer that listens for data has encountered an
> error.
> >
> > See also the link below for detailed information about NetDDE.
> >
> > Howard Hughes
> > We originally received events that the teamed nics had dropped their
> > links to the network. Upon their recovery we received the event id 206,
> > listen failed 15 (Source netdde). This event happens every 30 minutes.
> > To resolve, we restarted the NETdde service and the events quickly
> > subsided. Associated with this service is our Seagate Page Server that
> > is run on a number of our machines. It also needed to be restarted.
> > When restarting Netdde service, the Seagate Page Server was a dependent
> > and was restarted as well. I have seen some speculation that initial
> > cause of the disconnection of the nics is due to the binding order in
> > the advanced setting. I have swapped the binding order of the cpqteam
> > and tcpip objects to see if this resolves our initial problem. Also
> > instead of Load balancing the team, we are testing the fault tolerance
> > setting instead.
> > Links Dynamic Data Exchange (DDE) and NetDDE FAQ
> >
> >
> > latha wrote:
> >
> > > I was wondering if anyone can shine some light on this
> > > particular error message. I am not able to find much on
> > > this subject beyond the description of what NetDDE is.
> > >
> > > I started receiving this error message and at the same
> > > time I am not able to access one of the servers on our
> > > network. I am able to ping and connect to the server by
> > > using the ip address, but I can't do it via it's name.
> > > I know it is not a WINS problem and all of my network
> > > settings are correct.
> > >
> > > Source: NetDDE
> > > Event ID: 206
> > > Description: Listen failed: 15
> > >
> > > this error message appears in the eventvwr every 30
> > > minutes.
> > >
> > >
> >
>
> --------------------------------------------------------------------------
> --
> > > ----
> > >
> > >
> > > .
> > >
> > >
> >
> > --
> > "Don't lose sight of security. Security is a state of being,
> > not a state of budget. He with the most firewalls still does
> > not win. Put down that honeypot and keep up to date on your patches.
> > Demand better security from vendors and hold them responsible.
> > Use what you have, and make sure you know how to use it properly
> > and effectively."
> > ~Rain Forest Puppy
> >
http://www.wiretrip.net/rfp/txt/evolution.txt
> >
>
>