JJZolx;678883 Wrote:
Here's another bit of strangeness. The player actually 'sees' the
announced server on the remote network. I run several different servers
on the network (although only one is running at the moment) and just
changed the port forwarding to point at a different one. Each
Jeff Flowerday;679267 Wrote:
I had the same thing happening, it sees the name of the library but
would never connect. It turns out UDP packets weren't being forwarded
for 3483. Enabling them, fixed it right up.
So either you still don't have everything configured quite correct or
your
I just installed Wireshark on the server and see the UDP 3483 packets
coming in and being sent. Wireshark indicates that the outgoing packets
have bad header checksums, but I see that on every packet coming from
the server, including those from TCP port 9000. Says maybe caused by
IP checksum
emalvick;678902 Wrote:
Have you tried temporarily disabling the router firewall to see if it
will work without one?
I once had a problem with a Linksys router, and no matter what I did
with the ports, it wasn't until I turned the firewall off that I got
anything to work... Then (the
I can't for the life of me get this to work properly.
I'm not running a firewall on either the server or laptop. On the
hardware firewall at the server end I'm forwarding all external ports
to the server. I've set up a single, simple firewall rule to allow all
traffic to the IP address of the
Here's another bit of strangeness. The player actually 'sees' the
announced server on the remote network. I run several different servers
on the network (although only one is running at the moment) and just
changed the port forwarding to point at a different one. Each server
has a unique name and
JJZolx;678883 Wrote:
Here's another bit of strangeness. The player actually 'sees' the
announced server on the remote network. I run several different servers
on the network (although only one is running at the moment) and just
changed the port forwarding to point at a different one. Each
Have you tried temporarily disabling the router firewall to see if it
will work without one?
I once had a problem with a Linksys router, and no matter what I did
with the ports, it wasn't until I turned the firewall off that I got
anything to work... Then (the important part), once I turned
I'm spending the holidays at a relative's home and would like to stream
remotely to my laptop running SqueezePlay. I've enabled port forwarding
and added a couple of firewall rules to allow access to the server on my
LAN from the static IP address at his house.
From the remote location I can
Squeezeplay works this same way on my local network. From the WebUI I
can play music on SP on my laptop from my WHS2011 box, but SP itself on
my laptop thinks it's not connected. Since the SP player part works from
the WebUI I haven't really cared much about this.
--
w3wilkes
2 Duets - 1 for
Both TCP and UDP need to be forwarded for 9000 and 3483.
If you have the above configured properly. Disable firewall on your
computer, it's really redundant, your router is a firewall.
--
Jeff Flowerday
Jeff Flowerday's
Jeff Flowerday;678554 Wrote:
Both TCP and UDP need to be forwarded for 9000 and 3483.
If you have the above configured properly. Disable firewall on your
computer, it's really redundant, your router is a firewall.
UDP on 9000 is not required.
P
--
pski
real stereo doesn't just wake
12 matches
Mail list logo
