Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Curious | 33 comments | Create New Account
Click here to return to the 'Curious' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Curious
Authored by: Lizard_King on Dec 03, '02 03:26:43PM

Hmmm... This is definitely an interesting solution to this problem. I'm having difficulty understanding why these two services are related to connecting to an SMB share on that system.

DDE, or dynamic data exchange, is an old way for Windows programs to exchange information. From the MS site: "DDE is a form of interprocess communication that uses shared memory to exchange data between applications"

Now there is such a thing as DDE Shares, which is probably more related to this specific problem. Some more MS info:
"\\<ComputerName>\NDDE$
where <ComputerName> is the name of the computer running the server application. The NDDE$ indicates that the topic provided to DdeConnect is the DDE share name on the remote computer named <ComputerName>."

Can anyone shed some light for the techies?






[ Reply to This | # ]
Curious
Authored by: erm on Dec 03, '02 11:49:53PM

The only light I can shed is that it doesn't help. I tried enabling those services on a Win2K server and still got the -36 error while trying to connect. Frankly, I hadn't really dealy with this problem too much as I always anable afp (services for Macintosh) on any Win2K box that needs to serve Macs.



[ Reply to This | # ]
Curious
Authored by: ajmas on Dec 04, '02 08:12:55AM

Maybe it was doing this before, but I see my PC by name now. Since I have only one PC in my network I can't tell whether the changes had anything to do with this. Could someone please let me know if the change does effect the name in the connect to server dialogue?



[ Reply to This | # ]