UPnP problem: M-SEARCH but no NOTIFY

  • Thread starter Thread starter Jeff Van Epps
  • Start date Start date
J

Jeff Van Epps

Running XP SP3, trying to get some third party software to work which
will advertise itself as a UPnP device, which will then be used by a
PS3 on the network. Running Network Monitor on the PC, I can see that
it will send out M-SEARCH when it is looking for devices (PC wanting
to act as a client), and it receives M-SEARCH from the PS3, and it
receives NOTIFY from other network devices, but I never ever see the
PC sending a NOTIFY. The SSDP and UPnP Device Host services are set to
Automatic and are started. The Windows components "Internet Gateway
Device Discovery and Control Client" and "UPnP User Interface" are
both installed. The system has been restarted several times. A
different PC also running XP SP3 behaves the same. What are the
conditions for the PC sending a NOTIFY?
 
Running XP SP3, trying to get some third party software to work which
will advertise itself as a UPnP device, which will then be used by a
PS3 on the network. Running Network Monitor on the PC, I can see that
it will send out M-SEARCH when it is looking for devices (PC wanting
to act as a client), and it receives M-SEARCH from the PS3, and it
receives NOTIFY from other network devices, but I never ever see the
PC sending a NOTIFY. The SSDP and UPnP Device Host services are set to
Automatic and are started. The Windows components "Internet Gateway
Device Discovery and Control Client" and "UPnP User Interface" are
both installed. The system has been restarted several times. A
different PC also running XP SP3 behaves the same. What are the
conditions for the PC sending a NOTIFY?
Click to expand...

Maybe you should ask the author of the software this question.

- Thee Chicago Wolf [MVP]
 
Maybe you should ask the author of the software this question.
Click to expand...

They can't think of anything more to try than I've already done.

I've never written a UPnP device myself, but I thought that you just
registered with Windows as a device, and it took care of sending these
packets.
Does Windows advertise any of its own devices/services this way?
How can I demonstrate SSDP/UPnP working on my network without the
third party software? (divide and conquer)
 
Maybe you should ask the author of the software this question.
They can't think of anything more to try than I've already done.

I've never written a UPnP device myself, but I thought that you just
registered with Windows as a device, and it took care of sending these
packets.
Does Windows advertise any of its own devices/services this way?
How can I demonstrate SSDP/UPnP working on my network without the
third party software? (divide and conquer)
Click to expand...

This sounds to me like software trying to act like hardware. No wonder
it doesn't work properly. What software is this?

- Thee Chicago Wolf [MVP]
 
Let's forget the other software for now.
How can I demonstrate SSDP/UPnP working on my network using standard
Windows XP components?
 
Let's forget the other software for now.
How can I demonstrate SSDP/UPnP working on my network using standard
Windows XP components?
Click to expand...

Let's forget about this post as it's obvious you've got some shifty or
illegal "3rd party" app. Have fun Googling for a solution.

- Thee Chicago Wolf [MVP]
 
Let's forget about this post as it's obvious you've got some shifty or
illegal "3rd party" app. Have fun Googling for a solution.

- Thee Chicago Wolf [MVP]
Click to expand...

You have a seriously crappy attitude. First you try to pin blame on
the other software. Then you say "of course it won't work, it's
software trying to act like hardware". Then you accuse me of running
an illegal application. All without ever even attempting to help. As
an MVP, your attitude reflects negatively on Microsoft.

The software is DisplayShare. You can read all about it at www.displayshare..com.
Then you can come back here and tell me how shifty or illegal it is.

Now can get back to the problem? I would like to simplify it by not
involving the third party software. I will ask - for a third time - is
there any way to demonstrate that SSDP/UPnP is working using only
standard Windows XP components?

To all: I'm sorry you've had to endure this, and I hope that I haven't
let my own attitude taint this thread to the point where you would
rather just skip it than make a suggestion. Because I have googled
quite a bit looking for a solution and not found one, thus the cry for
help here.
 
You have a seriously crappy attitude. First you try to pin blame on
the other software. Then you say "of course it won't work, it's
software trying to act like hardware". Then you accuse me of running
an illegal application. All without ever even attempting to help. As
an MVP, your attitude reflects negatively on Microsoft.

The software is DisplayShare. You can read all about it at www.displayshare.com.
Then you can come back here and tell me how shifty or illegal it is.

Now can get back to the problem? I would like to simplify it by not
involving the third party software. I will ask - for a third time - is
there any way to demonstrate that SSDP/UPnP is working using only
standard Windows XP components?

To all: I'm sorry you've had to endure this, and I hope that I haven't
let my own attitude taint this thread to the point where you would
rather just skip it than make a suggestion. Because I have googled
quite a bit looking for a solution and not found one, thus the cry for
help here.
Click to expand...

Without information and giving me suspect answers, I am only lead to
one conclusion. As an MVP, I can only volunteer my time, irrespective
of Microsoft or their MPV program, to assist people with Windows
issues, not 3rd party software. Don't knock free help. No one here is
obligated to help you, MVP or not.

- Thee Chicago Wolf [MVP]
 
You have a seriously crappy attitude. First you try to pin blame on
the other software. Then you say "of course it won't work, it's
software trying to act like hardware". Then you accuse me of running
an illegal application. All without ever even attempting to help. As
an MVP, your attitude reflects negatively on Microsoft.

The software is DisplayShare. You can read all about it at www.displayshare.com.
Then you can come back here and tell me how shifty or illegal it is.

Now can get back to the problem? I would like to simplify it by not
involving the third party software. I will ask - for a third time - is
there any way to demonstrate that SSDP/UPnP is working using only
standard Windows XP components?

To all: I'm sorry you've had to endure this, and I hope that I haven't
let my own attitude taint this thread to the point where you would
rather just skip it than make a suggestion. Because I have googled
quite a bit looking for a solution and not found one, thus the cry for
help here.
Click to expand...

And while I'm at it, you need to monitor UDP port 1900 with some kind
of sniffing or port monitoring app to figure out why you're having
problems. That what SSDP broadcasts on when working in tandem with
UPnP.

- Thee Chicago Wolf [MVP]
 
And while I'm at it, you need to monitor UDP port 1900 with some kind
of sniffing or port monitoring app to figure out why you're having
problems. That what SSDP broadcasts on when working in tandem with
UPnP.
Click to expand...

Right, I am running (MS) Network Monitor (3.1) on the PC, as I
mentioned in the first post. I am monitoring port 1900. That is where
I see the PC sending M-SEARCH packets. I believe that happens when I
visit My Network Places. I never see the PC send a NOTIFY packet,
though I do see NOTIFY packets from other devices on the network.

What should I try next?
 
And while I'm at it, you need to monitor UDP port 1900 with some kind
Right, I am running (MS) Network Monitor (3.1) on the PC, as I
mentioned in the first post. I am monitoring port 1900. That is where
I see the PC sending M-SEARCH packets. I believe that happens when I
visit My Network Places. I never see the PC send a NOTIFY packet,
though I do see NOTIFY packets from other devices on the network.

What should I try next?
Click to expand...

NIC card driver up to date? Firmware on your network devices/router up
to date? Firewall allowing TCP/UDP port traffic on the network on port
1900? Your Firewall allowing traffic on port 1900? Have you tried
disabling the firewall on your PC? On your network device(s)? Does the
destination device have an IP? If so, can it be pinged? Can you telnet
to port 1900 on the destination device? Can you telnet to
127.0.0.0:1900? When you're attempting to connect to the destination
device, what does "netstat -a" show?

- Thee Chicago Wolf [MVP]
 
NIC card driver up to date? Firmware on your network devices/router up
to date? Firewall allowing TCP/UDP port traffic on the network on port
1900? Your Firewall allowing traffic on port 1900? Have you tried
disabling the firewall on your PC? On your network device(s)? Does the
destination device have an IP? If so, can it be pinged? Can you telnet
to port 1900 on the destination device? Can you telnet to
127.0.0.0:1900? When you're attempting to connect to the destination
device, what does "netstat -a" show?
Click to expand...

There is no firewall running on the PC.
The PC and other devices are on the same network switch (NetGear
NS105) so are all on the same side of the router (Linksys WRT<some
model>, running Tomato 1.22 firmware), so I don't think the router is
involved, but in any case it does have UPnP enabled. I have observed
traffic from the other devices (e.g. ReadyNAS Duo, DirecTV HR21) reach
port 1900 on the PC. Running Wireshark on a Linux box on the network I
have observed the PC's M-SEARCH packets, so port 1900 is getting out
of the PC as well. It simply isn't sending NOTIFYs.
There is no "destination device" - I want the *PC* to be a device/
service to which something else (PlayStation 3) connects.
From another computer, I can not telnet to port 1900 on the PC. I
won't be able to try it from the PC itself until tonight. However,
doesn't SSDP use connectionless UDP rather than TCP? If so, I wouldn't
expect telnet to work. But I don't claim to be an expert on SSDP and I
may be wrong.
The remaining details will have to wait until I get home tonight.
 
NIC card driver up to date? Firmware on your network devices/router up
There is no firewall running on the PC.
The PC and other devices are on the same network switch (NetGear
NS105) so are all on the same side of the router (Linksys WRT<some
model>, running Tomato 1.22 firmware), so I don't think the router is
involved, but in any case it does have UPnP enabled. I have observed
traffic from the other devices (e.g. ReadyNAS Duo, DirecTV HR21) reach
port 1900 on the PC. Running Wireshark on a Linux box on the network I
have observed the PC's M-SEARCH packets, so port 1900 is getting out
of the PC as well. It simply isn't sending NOTIFYs.
There is no "destination device" - I want the *PC* to be a device/
service to which something else (PlayStation 3) connects.
From another computer, I can not telnet to port 1900 on the PC. I
won't be able to try it from the PC itself until tonight. However,
doesn't SSDP use connectionless UDP rather than TCP? If so, I wouldn't
expect telnet to work. But I don't claim to be an expert on SSDP and I
may be wrong.
The remaining details will have to wait until I get home tonight.
Click to expand...

Tomato 1.22 is some hacked version of firmware, yes? Telneting to the
PC from shell / DOS will at least tell you it is accepting incoming
connection on TCP/UDP 1900. If you get no response, something's amuck
on the host PC.

What you're attempting to do is a bit beyond the scope of this group
and I'd say to dig through the KB on SSDP or search out forums of the
software where others are attempting to do what you're attempting to
do. Maybe also see if there's any hotfixes for this as well.

- Thee Chicago Wolf [MVP]
 
Back
Top