home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Support
Installation, configuration support
MP Client trying to connect to wrong address
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="PoBear" data-source="post: 1189658" data-attributes="member: 19817"><p>Thanks for your further thoughts on the problem.</p><p></p><p>To clarify the n/w issue. After the upgrade none of the other machines on the network were able to resolve the network name of the server, when you ping'd the machine by name it results in the wrong IP address being returned, one in the DHCP pool rather than the static address allocated, however, the machine has not had a DHCP address for over a year and the router, that allocates DHCP addresses has been factory reset in the last year, so there shouldn't even be a DHCP address.</p><p></p><p>I've had this on two computers, the server and my main MP client machine, both upgraded from W7 this week.</p><p></p><p>I've actually got around it by setting some of the other machines to a static IP, but doing so then means that they have the same problem as the original two. It's clearly a W10 problem but I don't think it is anything to do with upgrading as one of the machines now affected has only ever had W10 on it.</p></blockquote><p></p>
[QUOTE="PoBear, post: 1189658, member: 19817"] Thanks for your further thoughts on the problem. To clarify the n/w issue. After the upgrade none of the other machines on the network were able to resolve the network name of the server, when you ping'd the machine by name it results in the wrong IP address being returned, one in the DHCP pool rather than the static address allocated, however, the machine has not had a DHCP address for over a year and the router, that allocates DHCP addresses has been factory reset in the last year, so there shouldn't even be a DHCP address. I've had this on two computers, the server and my main MP client machine, both upgraded from W7 this week. I've actually got around it by setting some of the other machines to a static IP, but doing so then means that they have the same problem as the original two. It's clearly a W10 problem but I don't think it is anything to do with upgrading as one of the machines now affected has only ever had W10 on it. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
Installation, configuration support
MP Client trying to connect to wrong address
Contact us
RSS
Top
Bottom