Jamcast

Ive been impressed with Jamcast and thank you for the trial time. I have a couple of questions. I am using jamcast to stream spotify to my reciever. Even though it is in my house it seems to keep a tcp connection to an Akamai ip address open. Is this correct? If so why? Also, Im using Jamcast to stream to a Yamaha V671 AV reciever. When I first start jamcast after a minute or two it drops the connection with Jamcast, then keeps it fine once I connect again. Any ideas why or is this maybe just a yamaha thing.
Thanks for any help.

Using windows 7, I did a fresh restart without opening any programs, using windows resource monitor, I went to network tab, filtered for jamcast and found this as part of jamcasts tcp connections:

[System Process] 0 TCP towlie 49159 a23-49-45-15.deploy.akamaitechnologies.com http TIME_WAIT 1 88 1 1,369

whois gave me this information on the ip address.

General IP Information
IP: 23.49.45.15
Decimal: 389098767
Hostname: a23-49-45-15.deploy.akamaitechnologies.com
ISP: Akamai Technologies
Organization: Akamai Technologies
Services: None detected
Type: Corporate
Assignment: Static IP

My time has expired and Im unable to use jamcast, after a couple minutes its tcp/network usage drops off and this tcp connection ends. I am just curious about what info is being sent to and from akamai,
Thanks for your interest in this.

Thank you for the information. Ive ran adaware, malwarebytes, and anti virus, I do this regularly and glad to say its a clean machine. Tried some experiments. The ip address/connection to akamai only occurs durring the first 30 seconds to one minute of the startup of my Jamcast server. Ive tried this on a clean restart of the pc without the jamcast service enabled and there is no connection to the akamai ip address. When I restart the jamcast service in windows services the connection to akamai pops up and, goes to established, one packet is sent and one recieved, then it goes into time_wait and closes about 30 seconds later. I can stop the service either in jamcast or in windows services list and when I restart it, it does the same again. I have everything in jamcast/remote unchecked. Using SysInternals to identify the process associated with the tcp connection it identifies it as jamcastsvc.exe. So my ideas are, is this maybe something to do with the scrobble/Last.fm,it isnt checked to use. Also the podcast section doesnt appear to update itself every time the jamcast service is started, just once a day, but maybe that is using the connection to check itself? Any ideas on what else to check? This isnt a big deal and I like jamcast, I just like to know who my computer is talking too and find this stuff interesting
Thanks for any information on this.

Hi Quay,

Good deal, we can also use the network capture to understand that TCP connection you were inquiring about.

First, download Wireshark for free at http://www.wireshark.org/. This software has a lot of advanced features, but to do a simple network capture I think you'll have no trouble. Essentially, the procedure will be to start a new capture, reproduce the behavior we're interested in analyzing, and then stop the capture. Then, save the capture to disk and ZIP it up and email it to me at the support address below.

Ideally, your captures are as small as possible without missing the network traffic of interest, With respect to the TCP connection at service start, this will be easily accomplished -- stop the Jamcast service, initiate the capture, observe the TCP connection as you have in the past and stop the capture when the socket goes into the TIME_WAIT state.

For the dropped connections, it may prove to be a bit more challenging to isolate this without capture a huge amount of data. If you can somewhat predict the timing you might just restart the capture every couple of minutes until you're sure you've captured it.

I'll leave me instructions at that for now -- let me know you do and I'll be anxiously awaiting your results.

Thanks!

Hi Quay!

Sorry, I thought I still had the support email in my signature. It's support@sdstechnologies.com.

The startup connection to hostcollective is to here (our website), it's a ping to the Android locater services. We enable that ping by default but you can turn it off via the Network/Remote Access tab in Jamcast Server Manager. Try it, you should see that connection disappears.

Have fun!