Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Mooneyass]

So, I listen to my music collection at home from work using the Media Server and MC9.  To make my life easier, I have a DynDNS domain name and connect via that URL.  Anyway, for some reason my DynDNS updating app switched back to port 80 for updates.  The problem is, due to port blocking at work, I listen to my music on port 80.  Well, it seems that yesterday my DNS updater did it's thing whilst I was listening to my music and seems to have broken the Media server....  At least thats my thinking.  My last DynDNS update corresponds very closely (by memory) to when my music came to a crashing halt.

So, I've updated Media Center and restarted the machine but I still have no music.

Any ideas?  Do you think what I described is possible?  Should I uninstall/re-install?  Will I need a new key?

Thanks in advance,

Wes

[John Gateley]

Try debugging it first. Make sure the media server configuration is right, and
do "netstat -n" in a dos window to verify it is listening on the right port.

Try visiting via a browser (http://x.x.x.x:80/ where x.x.x.x is the IP address) to see if that gives you anything useful.

Are you running NAT of any sort?

j

[Mooneyass]

OK, I uninstalled fully, restarted, re-installed and got it all set up again.  I dont get the old TCP error that I was getting before but I still cant connect.

I tried logging in via my browser from within my LAN but got a page cannot be displayed.  The log from the sever states that it was accepting a connection when I tried logging in from work via MC9 and also recognized my browser attempt as an invalid connection type.  

I'm running a D-Link 614+ with port forwarding of port 80 to the music server.  All machines behind the router use static IP's.

netstat -n gives me my RDC and FTP info, no media server info.

Wes

[KingSparta]

another port, 81 maybe?

[Mooneyass]

Ok, looks as though it must be my D-Link router.  I rebooted my machine (1st time since re-install I believe) and I can see the media server in my browser (it asks me to login and I get action on netstat).  I'll give the router a reboot once I get home.  It does tend to be a bit flakey.  I'm VPN'd in from work right now so I cant do too much about it.

Thanks for the help, I'll post back if this solves the problem.

Wes

[KingSparta]

btw i use the

http://www.kana.homeip.net/

updater i like it alot better than the others i found, and it is free.

it als has more options

[Mooneyass]

Ok, found that I can reboot my router in the control panel but it didnt help.

I get this error when exiting the media server:
2/25/04 11:26:50 - bad port <>
02/25/04 11:26:50 - tcp_write failed error=10038
02/25/04 11:26:50 - bad version
02/25/04 11:26:52 - Stopped auto response thread.

[KingSparta]

did you update both media center on the client and also on the host? if not it may\will not connect.

02/25/04 11:26:50 - bad version

[Mooneyass]

Yup, updated on both ends to .136

My VPN isnt working either.....  Anyone want a d-link router  

I was hoping to VPN in and try the local IP, but it seems the VPN has stopped working too.  For some reason my RDC still works though....  The funny thing is that I havent changed anything in weeks.  So, once I get home I can connect to the Media Server on the LAN and test it there.  I think the issue is with my router though...

[Mooneyass]

Well, in the last hour or so I've changed nothing on my home network but it just started working.   ?

So, knowing that I work for a large corporation with a tremendously small IS department, I'd have to point at the problem being here at work.  Shoot, our internet goes down at least once a day....

Makes sense.

Thanks for your help guys.

Wes