Print

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

[DWAnderson]

No way to connect a remote PC (i.e. one other than the one on which the server is running) to Media Server by referencing the name of the computer on the LAN, e.g. as \\COMPUTER:81 where "COMPUTER" is the name of the computer on the LAN and 81 is the port number the server has been set up to operate on. I believe this used to work, e.g. in Build 100.

[JimH]

Use the full name:

server.mynetwork.com:8100

[DWAnderson]

That works, but it effectively make me send requests to a server PC on my LAN out over the internet, subjecting me to lag and bandwidth limitations not present on my LAN.

Is it not possible to resolve local PC names like prior versions used to be able to do?

[Nikolay]

DWAnderson,

The only request to main server will be DNS look up. After that, Media Center will communicate directly with Media Server. The way you connect will not make any difference.

Nikolay

[DWAnderson]

DWAnderson,

The only request to main server will be DNS look up. After that, Media Center will communicate directly with Media Server. The way you connect will not make any difference.

Nikolay

That doesn't seem right to me and my tests of Media Server using the two different modes of addressing the server bear this out. For example, Media Server displays thumnails of photos much faster when I provide the local IP address than when I use the internet domain name.  Is there some other reason this would be the case?

[JimH]

Your router, your network, Microsoft, or an act of God.

[KingSparta]

>> or an act of God.
JimH you know thats a 4 letter word

BTW I have read that before in my house insurance.

the problem is what happens if you do not believe in god, is the contract void?

[JimH]

It's double jeopardy, I think.