DDE server

February 6, 2009 at 02:33:34
Specs: xp home, 768

When I shutdown xp yesterday evening I had trouble shutting down as a meesage saying that DDE Server had not shout down please wait.
ok I was not aware that I am runnung a DDE server?

here is what netstat -a shows today after reboot.

------------------
I rebooted my computer and ran netstat -a this is what I got without opening a broswer
I have skype and vmware worstation on my computer see another netstat session below
I have a static ip going through a router.windows has a firewall as does the router

Microsoft(R) Windows DOS
(C)Copyright Microsoft Corp 1990-2001.

C:\DOCUME~1\NOW>netstat -a

Active Connections

Proto Local Address Foreign Address State
TCP whatnow:epmap whatnow:0 LISTENING
TCP whatnow:microsoft-ds whatnow:0 LISTENING
TCP whatnow:912 whatnow:0 LISTENING
TCP whatnow:1025 localhost:1026 ESTABLISHED
TCP whatnow:1026 localhost:1025 ESTABLISHED
TCP whatnow:1036 localhost:1037 ESTABLISHED
TCP whatnow:1037 localhost:1036 ESTABLISHED
TCP whatnow:1057 whatnow:0 LISTENING
TCP whatnow:6498 whatnow:0 LISTENING
TCP whatnow:netbios-ssn whatnow:0 LISTENING
TCP whatnow:1028 72.26.202.96:http TIME_WAIT
TCP whatnow:1029 208.43.240.248-static.reverse.softlayer.com:http
TIME_WAIT
TCP whatnow:1045 cpc2-rdng10-0-0-cust874.winn.cable.ntl.com:13241
TIME_WAIT
TCP whatnow:netbios-ssn whatnow:0 LISTENING
TCP whatnow:netbios-ssn whatnow:0 LISTENING
UDP whatnow:microsoft-ds *:*
UDP whatnow:isakmp *:*
UDP whatnow:1027 *:*
UDP whatnow:4500 *:*
UDP whatnow:ntp *:*
UDP whatnow:1900 *:*
UDP whatnow:ntp *:*
UDP whatnow:netbios-ns *:*
UDP whatnow:netbios-dgm *:*
UDP whatnow:1900 *:*
UDP whatnow:ntp *:*
UDP whatnow:netbios-ns *:*
UDP whatnow:netbios-dgm *:*
UDP whatnow:1900 *:*
UDP whatnow:ntp *:*
UDP whatnow:netbios-ns *:*
UDP whatnow:netbios-dgm *:*
UDP whatnow:1900 *:*


I ran nestat -a again 5 minutes after reboot still no web browswer open
I think under udp i have ntp showing??

C:\DOCUME~1\NOW>

Proto Local Address Foreign Address State
TCP whatnow:epmap whatnow:0 LISTENING
TCP whatnow:microsoft-ds whatnow:0 LISTENING
TCP whatnow:912 whatnow:0 LISTENING
TCP whatnow:1025 localhost:1026 ESTABLISHED
TCP whatnow:1026 localhost:1025 ESTABLISHED
TCP whatnow:1036 localhost:1037 ESTABLISHED
TCP whatnow:1037 localhost:1036 ESTABLISHED
TCP whatnow:1057 whatnow:0 LISTENING
TCP whatnow:6498 whatnow:0 LISTENING
TCP whatnow:netbios-ssn whatnow:0 LISTENING
TCP whatnow:netbios-ssn whatnow:0 LISTENING
TCP whatnow:netbios-ssn whatnow:0 LISTENING
UDP whatnow:microsoft-ds *:*
UDP whatnow:isakmp *:*
UDP whatnow:1027 *:*
UDP whatnow:4500 *:*
UDP whatnow:ntp *:*
UDP whatnow:1900 *:*
UDP whatnow:ntp *:*
UDP whatnow:netbios-ns *:*
UDP whatnow:netbios-dgm *:*
UDP whatnow:1900 *:*
UDP whatnow:ntp *:*
UDP whatnow:netbios-ns *:*
UDP whatnow:netbios-dgm *:*
UDP whatnow:1900 *:*
UDP whatnow:ntp *:*
UDP whatnow:netbios-ns *:*
UDP whatnow:netbios-dgm *:*
UDP whatnow:1900 *:*


See More: DDE server

Report •


#1
February 6, 2009 at 13:37:56

Dynamic Data Exchange, DDE is a mouse or some other input or MMI device.

"Best Practices", Event viewer, host file, perfmon, antivirus, anti-spyware, Live CD's, backups, are in my top 10


Report •

#2
February 6, 2009 at 13:58:09

DDE is a method of transferring Data from one application to another. It is largely obsolete now having been superseded by COM and OLE.

The DDE server is the application providing the Data and the DDE client is the application receiving it.

There is a NetDDE version which is used to exchange data between application over a network. If netDDE is running you will see NDDE* if your list of running processes.

Check out this KB from Microsoft my throw some light on the subject.

http://support.microsoft.com/kb/892850

Stuart


Report •

Related Solutions


Ask Question