failed to bind socket: 10013

Post Reply
siberian.pro

failed to bind socket: 10013

Post by siberian.pro »

Доброго времени суток всем

У меня проблема запуска HMS на пропатченную Windows XP.

Симптомы по шагам:

1) установил HMS на чистую, только что установленную из дистрибутива Windows XP SP3. Сервер успешно запускается.

2) В операционке само собой включено автоматическое обновление (Automatic Updates).
После обновления операционкой самой себя всеми патчами сервер больше не запускается аргументируя это слелующим образом:

12:06:52:390 Sender: THmsUDPSocket.SetupSocket
failed to bind socket: 10013
.
.
.
12:06:53:593 Sender: THmsSSDPControl.SendByeBye
Leave
THmsSSDPControl.Start: SetupSocket failed - проверьте список допустимых подключений на странице настройки Сервер.

3) Вручную удаляю все обновления системы. Сервер опять успешно запускается.

Необновленную операционку с незакрытыми дырками безопасности держать не хочется.
Буду благодарен если подскажете куда копать.

Ниже привожу полный лог:


Запуск программы
Запуск сервера
Запуск сервера [192.168.0.2]
12:06:52:375 Sender: THmsSubscriptionMgr.Create
start THmsSubscriptionMgr MainLoop
12:06:52:390 Sender: THmsHTTPServer.Start
HTTPServer работает
12:06:52:390 Sender: THmsUDPSocket.SetupSocket
failed to bind socket: 10013
12:06:52:390 Sender: AcceptLoop
listening on 192.168.0.2:40000
12:06:52:390 Sender: AcceptLoop
exiting accept loop
12:06:52:390 Sender: THmsHTTPServer.Stop
HTTPServer остановлен
12:06:52:390 Sender: THmsSSDPControl.CleanupSessions
Чистка сессий
12:06:52:390 Sender: THmsSSDPControl.Stop
SSDPController остановлен
12:06:52:390 Sender: THmsSSDPControl.SendByeBye
Enter
12:06:52:390 Sender: THmsUDPSocket.SendMulticast to 239.255.255.250:27655
NOTIFY * HTTP/1.1
NT: upnp:rootdevice
USN: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488::upnp:rootdevice
NTS: ssdp:byebye
HOST: 239.255.255.250:1900
Content-Length: 0, Result: Success


12:06:52:390 Sender: THmsUDPSocket.SendMulticast to 239.255.255.250:27655
NOTIFY * HTTP/1.1
NT: upnp:rootdevice
USN: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488::upnp:rootdevice
NTS: ssdp:byebye
HOST: 239.255.255.250:1900
Content-Length: 0, Result: Success


12:06:52:500 Sender: THmsUDPSocket.SendMulticast to 239.255.255.250:27655
NOTIFY * HTTP/1.1
NT: upnp:rootdevice
USN: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488::upnp:rootdevice
NTS: ssdp:byebye
HOST: 239.255.255.250:1900
Content-Length: 0, Result: Success


12:06:52:500 Sender: THmsUDPSocket.SendMulticast to 239.255.255.250:27655
NOTIFY * HTTP/1.1
NT: upnp:rootdevice
USN: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488::upnp:rootdevice
NTS: ssdp:byebye
HOST: 239.255.255.250:1900
Content-Length: 0, Result: Success


12:06:52:593 Sender: THmsUDPSocket.SendMulticast to 239.255.255.250:27655
NOTIFY * HTTP/1.1
NT: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488
USN: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488
NTS: ssdp:byebye
HOST: 239.255.255.250:1900
Content-Length: 0, Result: Success


12:06:52:593 Sender: THmsUDPSocket.SendMulticast to 239.255.255.250:27655
NOTIFY * HTTP/1.1
NT: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488
USN: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488
NTS: ssdp:byebye
HOST: 239.255.255.250:1900
Content-Length: 0, Result: Success


12:06:52:687 Sender: THmsUDPSocket.SendMulticast to 239.255.255.250:27655
NOTIFY * HTTP/1.1
NT: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488
USN: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488
NTS: ssdp:byebye
HOST: 239.255.255.250:1900
Content-Length: 0, Result: Success


12:06:52:687 Sender: THmsUDPSocket.SendMulticast to 239.255.255.250:27655
NOTIFY * HTTP/1.1
NT: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488
USN: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488
NTS: ssdp:byebye
HOST: 239.255.255.250:1900
Content-Length: 0, Result: Success


12:06:52:796 Sender: THmsUDPSocket.SendMulticast to 239.255.255.250:27655
NOTIFY * HTTP/1.1
NT: urn:schemas-upnp-org:device:MediaServer:1
USN: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488::urn:schemas-upnp-org:device:MediaServer:1
NTS: ssdp:byebye
HOST: 239.255.255.250:1900
Content-Length: 0, Result: Success


12:06:52:796 Sender: THmsUDPSocket.SendMulticast to 239.255.255.250:27655
NOTIFY * HTTP/1.1
NT: urn:schemas-upnp-org:device:MediaServer:1
USN: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488::urn:schemas-upnp-org:device:MediaServer:1
NTS: ssdp:byebye
HOST: 239.255.255.250:1900
Content-Length: 0, Result: Success


12:06:52:890 Sender: THmsUDPSocket.SendMulticast to 239.255.255.250:27655
NOTIFY * HTTP/1.1
NT: urn:schemas-upnp-org:device:MediaServer:1
USN: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488::urn:schemas-upnp-org:device:MediaServer:1
NTS: ssdp:byebye
HOST: 239.255.255.250:1900
Content-Length: 0, Result: Success


12:06:52:890 Sender: THmsUDPSocket.SendMulticast to 239.255.255.250:27655
NOTIFY * HTTP/1.1
NT: urn:schemas-upnp-org:device:MediaServer:1
USN: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488::urn:schemas-upnp-org:device:MediaServer:1
NTS: ssdp:byebye
HOST: 239.255.255.250:1900
Content-Length: 0, Result: Success


12:06:53:000 Sender: THmsUDPSocket.SendMulticast to 239.255.255.250:27655
NOTIFY * HTTP/1.1
NT: urn:schemas-upnp-org:service:ContentDirectory:1
USN: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488::urn:schemas-upnp-org:service:ContentDirectory:1
NTS: ssdp:byebye
HOST: 239.255.255.250:1900
Content-Length: 0, Result: Success


12:06:53:000 Sender: THmsUDPSocket.SendMulticast to 239.255.255.250:27655
NOTIFY * HTTP/1.1
NT: urn:schemas-upnp-org:service:ContentDirectory:1
USN: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488::urn:schemas-upnp-org:service:ContentDirectory:1
NTS: ssdp:byebye
HOST: 239.255.255.250:1900
Content-Length: 0, Result: Success


12:06:53:093 Sender: THmsUDPSocket.SendMulticast to 239.255.255.250:27655
NOTIFY * HTTP/1.1
NT: urn:schemas-upnp-org:service:ContentDirectory:1
USN: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488::urn:schemas-upnp-org:service:ContentDirectory:1
NTS: ssdp:byebye
HOST: 239.255.255.250:1900
Content-Length: 0, Result: Success


12:06:53:093 Sender: THmsUDPSocket.SendMulticast to 239.255.255.250:27655
NOTIFY * HTTP/1.1
NT: urn:schemas-upnp-org:service:ContentDirectory:1
USN: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488::urn:schemas-upnp-org:service:ContentDirectory:1
NTS: ssdp:byebye
HOST: 239.255.255.250:1900
Content-Length: 0, Result: Success


12:06:53:203 Sender: THmsUDPSocket.SendMulticast to 239.255.255.250:27655
NOTIFY * HTTP/1.1
NT: urn:schemas-upnp-org:service:ConnectionManager:1
USN: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488::urn:schemas-upnp-org:service:ConnectionManager:1
NTS: ssdp:byebye
HOST: 239.255.255.250:1900
Content-Length: 0, Result: Success


12:06:53:203 Sender: THmsUDPSocket.SendMulticast to 239.255.255.250:27655
NOTIFY * HTTP/1.1
NT: urn:schemas-upnp-org:service:ConnectionManager:1
USN: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488::urn:schemas-upnp-org:service:ConnectionManager:1
NTS: ssdp:byebye
HOST: 239.255.255.250:1900
Content-Length: 0, Result: Success


12:06:53:296 Sender: THmsUDPSocket.SendMulticast to 239.255.255.250:27655
NOTIFY * HTTP/1.1
NT: urn:schemas-upnp-org:service:ConnectionManager:1
USN: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488::urn:schemas-upnp-org:service:ConnectionManager:1
NTS: ssdp:byebye
HOST: 239.255.255.250:1900
Content-Length: 0, Result: Success


12:06:53:296 Sender: THmsUDPSocket.SendMulticast to 239.255.255.250:27655
NOTIFY * HTTP/1.1
NT: urn:schemas-upnp-org:service:ConnectionManager:1
USN: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488::urn:schemas-upnp-org:service:ConnectionManager:1
NTS: ssdp:byebye
HOST: 239.255.255.250:1900
Content-Length: 0, Result: Success


12:06:53:406 Sender: THmsUDPSocket.SendMulticast to 239.255.255.250:27655
NOTIFY * HTTP/1.1
NT: urn:microsoft.com:service:X_MS_MediaReceiverRegistrar:1
USN: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488::urn:microsoft.com:service:X_MS_MediaReceiverRegistrar:1
NTS: ssdp:byebye
HOST: 239.255.255.250:1900
Content-Length: 0, Result: Success


12:06:53:406 Sender: THmsUDPSocket.SendMulticast to 239.255.255.250:27655
NOTIFY * HTTP/1.1
NT: urn:microsoft.com:service:X_MS_MediaReceiverRegistrar:1
USN: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488::urn:microsoft.com:service:X_MS_MediaReceiverRegistrar:1
NTS: ssdp:byebye
HOST: 239.255.255.250:1900
Content-Length: 0, Result: Success


12:06:53:500 Sender: THmsUDPSocket.SendMulticast to 239.255.255.250:27655
NOTIFY * HTTP/1.1
NT: urn:microsoft.com:service:X_MS_MediaReceiverRegistrar:1
USN: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488::urn:microsoft.com:service:X_MS_MediaReceiverRegistrar:1
NTS: ssdp:byebye
HOST: 239.255.255.250:1900
Content-Length: 0, Result: Success


12:06:53:500 Sender: THmsUDPSocket.SendMulticast to 239.255.255.250:27655
NOTIFY * HTTP/1.1
NT: urn:microsoft.com:service:X_MS_MediaReceiverRegistrar:1
USN: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488::urn:microsoft.com:service:X_MS_MediaReceiverRegistrar:1
NTS: ssdp:byebye
HOST: 239.255.255.250:1900
Content-Length: 0, Result: Success


12:06:53:593 Sender: THmsSSDPControl.SendByeBye
Leave
THmsSSDPControl.Start: SetupSocket failed - проверьте список допустимых подключений на странице настройки Сервер.
Top
siberian.pro

Re: failed to bind socket: 10013

Post by siberian.pro »

Отключение файрвола ситуации не меняет
Top
Eugene
Posts: 2805
Joined: Tue Sep 16, 2008 7:30 pm

Re: failed to bind socket: 10013

Post by Eugene »

siberian.pro wrote: У меня проблема запуска HMS на пропатченную Windows XP.

Симптомы по шагам:

1) установил HMS на чистую, только что установленную из дистрибутива Windows XP SP3. Сервер успешно запускается.

2) В операционке само собой включено автоматическое обновление (Automatic Updates).
После обновления операционкой самой себя всеми патчами сервер больше не запускается аргументируя это слелующим образом:

12:06:52:390 Sender: THmsUDPSocket.SetupSocket
failed to bind socket: 10013
.
.
.
12:06:53:593 Sender: THmsSSDPControl.SendByeBye
Leave
THmsSSDPControl.Start: SetupSocket failed - проверьте список допустимых подключений на странице настройки Сервер.

3) Вручную удаляю все обновления системы. Сервер опять успешно запускается.

Необновленную операционку с незакрытыми дырками безопасности держать не хочется.
Буду благодарен если подскажете куда копать.

Ниже привожу полный лог:


Запуск программы
Запуск сервера
Запуск сервера [192.168.0.2]
12:06:52:375 Sender: THmsSubscriptionMgr.Create
start THmsSubscriptionMgr MainLoop
12:06:52:390 Sender: THmsHTTPServer.Start
HTTPServer работает
12:06:52:390 Sender: THmsUDPSocket.SetupSocket
failed to bind socket: 10013
12:06:52:390 Sender: AcceptLoop
listening on 192.168.0.2:40000
12:06:52:390 Sender: AcceptLoop
exiting accept loop
12:06:52:390 Sender: THmsHTTPServer.Stop
HTTPServer остановлен
12:06:52:390 Sender: THmsSSDPControl.CleanupSessions
Чистка сессий
12:06:52:390 Sender: THmsSSDPControl.Stop
SSDPController остановлен
12:06:52:390 Sender: THmsSSDPControl.SendByeBye
Enter
12:06:52:390 Sender: THmsUDPSocket.SendMulticast to 239.255.255.250:27655
NOTIFY * HTTP/1.1
NT: upnp:rootdevice
USN: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488::upnp:rootdevice
NTS: ssdp:byebye
HOST: 239.255.255.250:1900
Content-Length: 0, Result: Success


12:06:52:390 Sender: THmsUDPSocket.SendMulticast to 239.255.255.250:27655
NOTIFY * HTTP/1.1
NT: upnp:rootdevice
USN: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488::upnp:rootdevice
NTS: ssdp:byebye
HOST: 239.255.255.250:1900
Content-Length: 0, Result: Success


12:06:52:500 Sender: THmsUDPSocket.SendMulticast to 239.255.255.250:27655
NOTIFY * HTTP/1.1
NT: upnp:rootdevice
USN: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488::upnp:rootdevice
NTS: ssdp:byebye
HOST: 239.255.255.250:1900
Content-Length: 0, Result: Success


12:06:52:500 Sender: THmsUDPSocket.SendMulticast to 239.255.255.250:27655
NOTIFY * HTTP/1.1
NT: upnp:rootdevice
USN: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488::upnp:rootdevice
NTS: ssdp:byebye
HOST: 239.255.255.250:1900
Content-Length: 0, Result: Success


12:06:52:593 Sender: THmsUDPSocket.SendMulticast to 239.255.255.250:27655
NOTIFY * HTTP/1.1
NT: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488
USN: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488
NTS: ssdp:byebye
HOST: 239.255.255.250:1900
Content-Length: 0, Result: Success


12:06:52:593 Sender: THmsUDPSocket.SendMulticast to 239.255.255.250:27655
NOTIFY * HTTP/1.1
NT: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488
USN: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488
NTS: ssdp:byebye
HOST: 239.255.255.250:1900
Content-Length: 0, Result: Success


12:06:52:687 Sender: THmsUDPSocket.SendMulticast to 239.255.255.250:27655
NOTIFY * HTTP/1.1
NT: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488
USN: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488
NTS: ssdp:byebye
HOST: 239.255.255.250:1900
Content-Length: 0, Result: Success


12:06:52:687 Sender: THmsUDPSocket.SendMulticast to 239.255.255.250:27655
NOTIFY * HTTP/1.1
NT: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488
USN: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488
NTS: ssdp:byebye
HOST: 239.255.255.250:1900
Content-Length: 0, Result: Success


12:06:52:796 Sender: THmsUDPSocket.SendMulticast to 239.255.255.250:27655
NOTIFY * HTTP/1.1
NT: urn:schemas-upnp-org:device:MediaServer:1
USN: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488::urn:schemas-upnp-org:device:MediaServer:1
NTS: ssdp:byebye
HOST: 239.255.255.250:1900
Content-Length: 0, Result: Success


12:06:52:796 Sender: THmsUDPSocket.SendMulticast to 239.255.255.250:27655
NOTIFY * HTTP/1.1
NT: urn:schemas-upnp-org:device:MediaServer:1
USN: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488::urn:schemas-upnp-org:device:MediaServer:1
NTS: ssdp:byebye
HOST: 239.255.255.250:1900
Content-Length: 0, Result: Success


12:06:52:890 Sender: THmsUDPSocket.SendMulticast to 239.255.255.250:27655
NOTIFY * HTTP/1.1
NT: urn:schemas-upnp-org:device:MediaServer:1
USN: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488::urn:schemas-upnp-org:device:MediaServer:1
NTS: ssdp:byebye
HOST: 239.255.255.250:1900
Content-Length: 0, Result: Success


12:06:52:890 Sender: THmsUDPSocket.SendMulticast to 239.255.255.250:27655
NOTIFY * HTTP/1.1
NT: urn:schemas-upnp-org:device:MediaServer:1
USN: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488::urn:schemas-upnp-org:device:MediaServer:1
NTS: ssdp:byebye
HOST: 239.255.255.250:1900
Content-Length: 0, Result: Success


12:06:53:000 Sender: THmsUDPSocket.SendMulticast to 239.255.255.250:27655
NOTIFY * HTTP/1.1
NT: urn:schemas-upnp-org:service:ContentDirectory:1
USN: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488::urn:schemas-upnp-org:service:ContentDirectory:1
NTS: ssdp:byebye
HOST: 239.255.255.250:1900
Content-Length: 0, Result: Success


12:06:53:000 Sender: THmsUDPSocket.SendMulticast to 239.255.255.250:27655
NOTIFY * HTTP/1.1
NT: urn:schemas-upnp-org:service:ContentDirectory:1
USN: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488::urn:schemas-upnp-org:service:ContentDirectory:1
NTS: ssdp:byebye
HOST: 239.255.255.250:1900
Content-Length: 0, Result: Success


12:06:53:093 Sender: THmsUDPSocket.SendMulticast to 239.255.255.250:27655
NOTIFY * HTTP/1.1
NT: urn:schemas-upnp-org:service:ContentDirectory:1
USN: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488::urn:schemas-upnp-org:service:ContentDirectory:1
NTS: ssdp:byebye
HOST: 239.255.255.250:1900
Content-Length: 0, Result: Success


12:06:53:093 Sender: THmsUDPSocket.SendMulticast to 239.255.255.250:27655
NOTIFY * HTTP/1.1
NT: urn:schemas-upnp-org:service:ContentDirectory:1
USN: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488::urn:schemas-upnp-org:service:ContentDirectory:1
NTS: ssdp:byebye
HOST: 239.255.255.250:1900
Content-Length: 0, Result: Success


12:06:53:203 Sender: THmsUDPSocket.SendMulticast to 239.255.255.250:27655
NOTIFY * HTTP/1.1
NT: urn:schemas-upnp-org:service:ConnectionManager:1
USN: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488::urn:schemas-upnp-org:service:ConnectionManager:1
NTS: ssdp:byebye
HOST: 239.255.255.250:1900
Content-Length: 0, Result: Success


12:06:53:203 Sender: THmsUDPSocket.SendMulticast to 239.255.255.250:27655
NOTIFY * HTTP/1.1
NT: urn:schemas-upnp-org:service:ConnectionManager:1
USN: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488::urn:schemas-upnp-org:service:ConnectionManager:1
NTS: ssdp:byebye
HOST: 239.255.255.250:1900
Content-Length: 0, Result: Success


12:06:53:296 Sender: THmsUDPSocket.SendMulticast to 239.255.255.250:27655
NOTIFY * HTTP/1.1
NT: urn:schemas-upnp-org:service:ConnectionManager:1
USN: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488::urn:schemas-upnp-org:service:ConnectionManager:1
NTS: ssdp:byebye
HOST: 239.255.255.250:1900
Content-Length: 0, Result: Success


12:06:53:296 Sender: THmsUDPSocket.SendMulticast to 239.255.255.250:27655
NOTIFY * HTTP/1.1
NT: urn:schemas-upnp-org:service:ConnectionManager:1
USN: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488::urn:schemas-upnp-org:service:ConnectionManager:1
NTS: ssdp:byebye
HOST: 239.255.255.250:1900
Content-Length: 0, Result: Success


12:06:53:406 Sender: THmsUDPSocket.SendMulticast to 239.255.255.250:27655
NOTIFY * HTTP/1.1
NT: urn:microsoft.com:service:X_MS_MediaReceiverRegistrar:1
USN: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488::urn:microsoft.com:service:X_MS_MediaReceiverRegistrar:1
NTS: ssdp:byebye
HOST: 239.255.255.250:1900
Content-Length: 0, Result: Success


12:06:53:406 Sender: THmsUDPSocket.SendMulticast to 239.255.255.250:27655
NOTIFY * HTTP/1.1
NT: urn:microsoft.com:service:X_MS_MediaReceiverRegistrar:1
USN: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488::urn:microsoft.com:service:X_MS_MediaReceiverRegistrar:1
NTS: ssdp:byebye
HOST: 239.255.255.250:1900
Content-Length: 0, Result: Success


12:06:53:500 Sender: THmsUDPSocket.SendMulticast to 239.255.255.250:27655
NOTIFY * HTTP/1.1
NT: urn:microsoft.com:service:X_MS_MediaReceiverRegistrar:1
USN: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488::urn:microsoft.com:service:X_MS_MediaReceiverRegistrar:1
NTS: ssdp:byebye
HOST: 239.255.255.250:1900
Content-Length: 0, Result: Success


12:06:53:500 Sender: THmsUDPSocket.SendMulticast to 239.255.255.250:27655
NOTIFY * HTTP/1.1
NT: urn:microsoft.com:service:X_MS_MediaReceiverRegistrar:1
USN: uuid:ecbf19f3-acf7-4ac3-b32d-aa1408745488::urn:microsoft.com:service:X_MS_MediaReceiverRegistrar:1
NTS: ssdp:byebye
HOST: 239.255.255.250:1900
Content-Length: 0, Result: Success


12:06:53:593 Sender: THmsSSDPControl.SendByeBye
Leave
THmsSSDPControl.Start: SetupSocket failed - проверьте список допустимых подключений на странице настройки Сервер.
Список допустимых подключений на странице настройки Сервер проверили ?
Top
siberian.pro

Re: failed to bind socket: 10013

Post by siberian.pro »

Проверил, сервер настроен на единственный адрес 192.168.0.2.
Согласно логам вроде запускается на 192.168.0.2
Attachments
img.JPG
img.JPG (63.11 KiB) Viewed 15637 times
Top
Eugene
Posts: 2805
Joined: Tue Sep 16, 2008 7:30 pm

Re: failed to bind socket: 10013

Post by Eugene »

siberian.pro wrote:Проверил, сервер настроен на единственный адрес 192.168.0.2.
Согласно логам вроде запускается на 192.168.0.2
На этой странице можно включить режим "Использовать адрес 0.0.0.0..".
Ошибка связана с отказом в получении UPnP - сообщений, возможно связана с Windows Firewall, возможно с другими приложениями. Проверить можно, например, в TcpView, строки вида UDP имя_компьютера:1900 *.*. Наверно при запуске сервера, появилось окошко Windows Firewall, что ответили ?
Top
siberian.pro

Re: failed to bind socket: 10013

Post by siberian.pro »

Окошко файрвола появлялось, ответил разрешить (Allow)
Выше уже писал "Отключение файрвола ситуации не меняет"
В списке разрешений файрвола есть Home Media Server (разрешено все) и UPnP Infrastructure

Попробую отключить остальные UPnP службы XP, в прошлый раз помогло с TVersity
Top
Post Reply

Return to “Общие решения”