DirectPlay8 error in dxdiag


Recommended Posts

I've got a curious problem.

I'm in the process of adjusting my hard drives etc so I don't have any network-capable games to test it on but after running dxdiag to check that the Dec 2005 update for DirectX 9.0c installed properly I noticed this:

"The registry information for the service provider 'DirectPlay8 IPX Service Provider' is missing or damaged.

You should reinstall DirectX.

The registry information for the service provider 'DirectPlay8 TCP/IP Service Provider' is missing or damaged.

You should reinstall DirectX. You should reinstall DirectX to get the latest version."

The affected file is

"DirectPlay8 IPX Service Provider - Registry: Error, File: dpnwsock.dll (5.01.2600.0000)

DirectPlay8 TCP/IP Service Provider - Registry: Error, File: dpnwsock.dll (5.01.2600.0000)"

The file version of the other files is "5.03.2600.2180" but I'm unsure whether these files have been updated etc. so I don't think it's an issue.

I've reinstalled the Directx 9.0C December 2005 redist and it doesn't fix the issue.

As an aside, I have got the TCP/IP NETBIOS service set to disabled but enabling the service didn't fix it either. I have it disabled because it is not needed for my router.

Will this registry issue cause problems with online games? I've googled it and this error seems to cause problems with some online games.

I've looked in the corresponding registry entries for this part of DirectX 9.0c at:

"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DirectPlay8"

and the values are as follows:

"[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DirectPlay8]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DirectPlay8\Applications]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DirectPlay8\Service Providers]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DirectPlay8\Service Providers\DPNSPModemModem]

"Friendly Name"="DirectPlay8 Modem Service Provider"

"GUID"="{6D4A3650-628D-11D2-AE0F-006097B01411}"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DirectPlay8\Service Providers\DPNSPModemSerial]

"Friendly Name"="DirectPlay8 Serial Service Provider"

"GUID"="{743B5D60-628D-11D2-AE0F-006097B01411}"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DirectPlay8\Service Providers\DPNSPWinsockIPX]

"Friendly Name"="DirectPlay8 IPX Service Provider"

"GUID"="{53934290-628D-11D2-AE0F-006097B01411}"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DirectPlay8\Service Providers\DPNSPWinsockTCP]

"Friendly Name"="DirectPlay8 TCP/IP Service Provider"

"GUID"="{EBFE7BA0-628D-11D2-AE0F-006097B01411}"

I've done a further registry search and the GUID entries all point to Modem-related registry CLID's and the file "dpnet.dll" which dxdiag says is fine.

I use a Netgear Wireless Router to get online so I'm hoping the issue is specifically a dial-up modem related issue but with MS you can never be too sure!

Can someone look at the same registry entries as above on their system and report any differences?

Thanks in advance for any help :)

Link to comment
Share on other sites

This is what I have on my system, a stand alone PC. XP SP2 + all updates. DirectX9c December update installed. No problems. I don't have dpnwsock.dll showing in directX files, I have dpwsock.dll and dpwsockx.dll, it is this latter one that appears to be used. I connect to the intenet (broadband) vis a USB DSL modem; no router. TCP/IP Netbios service is disabled.

The dxdiag saved file includes this section:

DirectPlay Service Providers

----------------------------

DirectPlay8 Modem Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.2180)

DirectPlay8 Serial Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.2180)

DirectPlay8 IPX Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.2180)

DirectPlay8 TCP/IP Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.2180)

Internet TCP/IP Connection For DirectPlay - Registry: OK, File: dpwsockx.dll (5.03.2600.2180)

IPX Connection For DirectPlay - Registry: OK, File: dpwsockx.dll (5.03.2600.2180)

Modem Connection For DirectPlay - Registry: OK, File: dpmodemx.dll (5.03.2600.2180)

Serial Connection For DirectPlay - Registry: OK, File: dpmodemx.dll (5.03.2600.2180)

These are the registry entries at DirectPlay8. As far as I can tell it's the same as yours.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DirectPlay8]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DirectPlay8\Applications]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DirectPlay8\Service Providers]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DirectPlay8\Service Providers\DPNSPModemModem]

"Friendly Name"="DirectPlay8 Modem Service Provider"

"GUID"="{6D4A3650-628D-11D2-AE0F-006097B01411}"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DirectPlay8\Service Providers\DPNSPModemSerial]

"Friendly Name"="DirectPlay8 Serial Service Provider"

"GUID"="{743B5D60-628D-11D2-AE0F-006097B01411}"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DirectPlay8\Service Providers\DPNSPWinsockIPX]

"Friendly Name"="DirectPlay8 IPX Service Provider"

"GUID"="{53934290-628D-11D2-AE0F-006097B01411}"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DirectPlay8\Service Providers\DPNSPWinsockTCP]

"Friendly Name"="DirectPlay8 TCP/IP Service Provider"

"GUID"="{EBFE7BA0-628D-11D2-AE0F-006097B01411}"

Have you tried the test directplay on the Network tab of dxdiag? It reported succesful for me.

Edited by JRosenfeld
Link to comment
Share on other sites

Hmmmmm, the DirectPlay test just says "The tests were cancelled before completion" but I don't really know what to do to use it properly.

It's weird that your results don't even mention "dpnwsock.dll" and instead rely on dnet.dll for DirectPlay8.

I'm tempted to delete "dpnwsock.dll" and see if that fixes it.

Link to comment
Share on other sites

Ahhh, fixed it!

After comparing the registry info supplied, I decided to check where the GUID's for DirectPlay8 IPX Service Provider & DirectPlay8 TCP/IP Service Provider pointed (GUID"="{53934290-628D-11D2-AE0F-006097B01411} & GUID"="{EBFE7BA0-628D-11D2-AE0F-006097B01411} respectively) and my versions all pointed to "dpnwsock.dll".

I simply edited the key to say "dpnet.dll" and dxdiag reported no problems.

I've got no idea why they changed to dpnwsock.dll...

Anyway, thanks JRosenfield for the help :)

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.