Print

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

[Robert Taylor]

Is there any way that I can get Media server to listen on two interfaces at the same time?

I have two machines connected via ethernet AND firewire.

IP is running on both interfaces (obviously they have two different addresses).

If I look at Media Server, the window says that it is sharing on the firewire IP address, but if I attempt to connect to this address using Media Center client, it doesn't see the server. It waits a short period, then reconnects to the server using the ethernet IP.

When I connect using the ethernet IP address it works fine.

Any ideas?

[JimH]

Media Server should normally share your files on the Ethernet address.

You can disable the Firewire connection (if you aren't using it) by right clicking on it in Network Connections.

[John Gateley]

Hi Lunchmeat,

This is a case I haven't tried, but Media Server should listen on both interfaces. If it is not responding on the firewire interface, make sure the network is set up correctly: try a different service. Weird things can happen when you have two interfaces (packets
sent to one interface may be returned via the other interface).

j

[Robert Taylor]

Both interfaces are definately functioning correctly. I use TightVNC to remote control all my PCs, and I can get to my Media Server machine via VNC using either interface with no problems.

It's no big deal, I was a bit curious that MS was displaying the IP address of the firewire interface in its title bar, but only seemed accessible from the ethernet IP.

Oh well...

[RemyJ]

It's always displayed only 1 interface.  I've got a regular 100mb ethernet, a gigabit ethernet, and a firewire interface and the server is working on all 3.  

Do a "netstat -an" from a command line and see if you can see it.   Setting the server to an obscure port will help.  It will also help detect if something else may be bound to the firewire interface on media server's port.

You can also try connecting using a regular browser.  You'll get a message like: "You are not using a standard Music01 protocol to access this server." or a "400" message if you have "friendly" HTTP error messages enabled in IE.

Are you connecting via DNS name or IP address?  If name, try address directly and see what happens.

[John Gateley]

RemyJ: Cool - it's one of those things that should work, but I never tested (I guess more personal machines are getting multiple interfaces now, use to be a router only thing).

Lunchmeat: are you using the auto-detect media server feature or entering the IP address/name by hand?

j

[RemyJ]

I have to clarify... I never use the auto detect because it doesn't work well with multiple interfaces.   The server will return the first interface it's bound to which may NOT be reachable from the client that initiated the request.  

[Robert Taylor]

Remy: I try connecting via IP address directly. I will check out the browser connection and netstat as suggested tonight...

John: I have seperate entries in my library manager, one for the ethernet IP, and one for the firewire IP...