A quick eyeball over your log shows there are a couple of problems. Most of the logging is for port 2869, which is used for a Microsoft protocol called SSDP which is a kind of name service for UPnP devices (so says dshield .org at Port 2869 (tcp/udp) Attack Activity - SANS Internet Storm Center). I’ll presume that is why your XBox is having such a problem.
I’m seeing several LAN addresses in your log. Unfortunately the log doesn’t tell us enough (that’s a known CFP annoyance), so I’m going to make a guess as to what machine is which. On your LAN, you have your router at 192.168.185.1, your PC at 192.168.185.100, and the Xbox at 192.168.185.102. With that guess, here’s what I’m suggesting for changes to your CFP rules.
First, let’s make sure of your LAN network zone. In CFP, click Firewall → MyNetworkZones, then for the entry that corresponds to your LAN, make sure it includes the full range of addresses 192.168.185.0 thru 192.168.185.255. The easy way to do that, is to click on the entry to highlight it, click edit, and then choose the button entry “IP address mask” and enter 192.168.185.0 / 255.255.255.0. That will pick up the entire range.
Next, we need to check your CFP Global Rules. Click CFP → Firewall → Advanced, and then the tab Global Rules. You need to allow traffic inbound to your PC from other devices on your LAN. The default is to pretty much block everything. You may need to add a rule to allow traffic from your LAN. If you do need to add a rules, then choose protocol IP rather than the default TCP or UDP. That’ll simplify some of the rules to allow the Xbox to talk to your PC.
Not knowing what rules you’ve got in place, I can’t really give a whole lot more detailed suggestions to walk you thru the changes. If you run the Config Reporting Script and post the result, then it’d be possible to go thru the firewall rules in detail.
The LAN rule settings should take care of the problem if you have a fairly straightforward rule set. Otherwise, it’s going to have to get down into the details.
What happens if you go to the “Stealth Ports Wizard” and choose the top choice Define a new trusted network/Next/I would like to trust an existing my network zone/From the drop down menu local area network # 1/ then next.This should add 2 new rules in Global Rules allowing communication within your LAN.
From your log, it looks like you’ll need to add at least two more rules. One rule to allow the SSDP traffic, and the other to allow ICMP traffic. Additional rules may be needed, but we’ll find that out as we go.
Duplicate your rule 2, but have the destination port be 2869 rather than 3074, and the source IP to be your LAN network zone. That should take care of the SSDP traffic, allowing the XBox to do name lookup.
Duplicate your rule 1, but have the protocol be ICMP rather than UDP, and have the source IP to be your LAN network zone. That should help in any error reporting, as ICMP is the means by which error messages get communicated between devices when there is a network problem.
Evidently the XBox needs something more. What’s in your CFP log now that you’ve got these additional rules in place?
An XBox is a very chatty device, and the Microsoft protocols have been compared to spaghetti, where everything has to be available on the plate, or nothing works. Without knowing what your rule set is via the Config Reporting Script, we’ll have to work thru the rules one at a time (new rule, still doesn’t work, show log, repeat) until everything gets to a working condition. It just takes a bunch of time and a lot of postings.
I was having the same problem but seem to have solved it. not sure if this is the best way, but here is what I did:
I am going to give EVERY SINGLE step to help out all those unfamiliar with COMODO (:HUG)
Open COMODO V3, goto FIREWALL>My Port Sets>ADD>A New Port Set…
In “Type name of Port Set” type “XBOX” and click apply
Scroll down till you can see the newly created “XBOX” port set, click on it then click ADD>A New Port…
Select “A single port” and enter port 2869. Click apply
Repeat steps 3 & 4 for ports 1900 and 10243.
Repeat steps 3 & 4 except for step 4 select “A port range” and enter port 10280 in the first box and port 10284 in the second
Click apply on the “My Port Sets” window.
Now return to the “FIREWALL” tab and under “Firewall Tasks” (on the left of the window) click advanced.
Click “Network Security Policy” and goto the “Global Rules” tab and click “Add”
Make sure the following settings are selected: “Actions” set as “Allow”, “Protocol” set as “TCP or UDP” and “Direction” set as “In/Out”
Enter XBOX as description
Select the “Source Address” tab
Select IP Range.
Now here you need to enter a range specific for your network, enter your IP range from “0” to “255”. (e.g. your IP should be something like 192.168.1.1 so if it was you would enter Start IP as 192.168.1.0 and enter End IP as 192.168.1.255, adjust this according to your IP. For TigerJon I think you will enter 192.168.185.0 to 192.168.185.255 from what I saw in your previous posts but I’m not rally not sure, if you find it doesn’t work check this step)
Select the “Destination Address” tab
Repeat steps 13 and 14 under this tab.
Click “Source Port” tab
Select “A Set of Ports” and select “XBOX” from the drop down list that appears.
Click “Destination Port” tab
Repeat step 18 under this tab.
Click apply.
That’s all I did and it works fine… hope it works for you. Let me know either way
Hello all…
I have a question… When I connect my pc to my xbox through an ethernet cable i am able to share…when I go wireless the xbox stops reading the pc…any ideas why…