Print

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

[XeWonder]

Good day,

My Library server is "serving" on ip address 0.0.0.0 instead of the proper ip address.... (probably because of vmware)

obviously nothing can see it... how can i force it so @bind to the proper IP address of my network?

Thanks

DD

[robydago]

0.0.0.0 means any ip\interface so the proper ip should be included

[XeWonder]

Every machine in the house can not find it!

but if i ge another machine to start a library, it works ok.

I think it's because with VMWare I have multiple cards...

Anyway... not working...

how can I bind MC to a particular interface?

[JimH]

Does the bottle you're running in have more than one network interface?

I believe MC uses the first it finds.

[robydago]

I think it's because with VMWare I have multiple cards...

did you try disabling them and then restarting MC?

[XeWonder]

Hi,

Yes, VMWare are all disabled.

I am using "cports" to see what is happening with my ip ports.

QUOTE
==================================================
Process Name      : Media Center 13.exe
Process ID        : 5612
Protocol          : TCP
Local Port        : 81
Local Port Name   : hosts2-ns
Local Address     : 0.0.0.0
Remote Port       :
Remote Port Name  :
Remote Address    : 0.0.0.0
Remote Host Name  :
State             : Listening
Process Path      : C:\Program Files\J River\Media Center 13\Media Center 13.exe
Product Name      : Media Center
File Description  : Media Center
File Version      : 13.0.152
Company           : JRiver, Inc.
Process Created On: 25/04/2009 07:49:09
User Name         : DDINTERNET\Administrator
Process Services  :
Process Attributes:
Added On          : 25/04/2009 07:50:19
Module Filename   :
Remote IP Country :
Window Title      : Media Center
==================================================

==================================================
Process Name      : Media Center 13.exe
Process ID        : 5612
Protocol          : UDP
Local Port        : 5556
Local Port Name   :
Local Address     : 0.0.0.0
Remote Port       :
Remote Port Name  :
Remote Address    :
Remote Host Name  :
State             :
Process Path      : C:\Program Files\J River\Media Center 13\Media Center 13.exe
Product Name      : Media Center
File Description  : Media Center
File Version      : 13.0.152
Company           : JRiver, Inc.
Process Created On: 25/04/2009 07:49:09
User Name         : DDINTERNET\Administrator
Process Services  :
Process Attributes:
Added On          : 25/04/2009 07:50:38
Module Filename   :
Remote IP Country :
Window Title      : Media Center
==================================================

UNQUOTE

Thanks

[XeWonder]

... and here is my ipconfig...

QUOTE

C:\>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : S1
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Unknown
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast Ethernet
NIC
   Physical Address. . . . . . . . . : 00-02-3F-14-98-AE
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 192.168.0.250
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.0.1

C:\>UNQUOTE

[XeWonder]

To Re-cap

MC running on Windows 2003 server 1 network card.

Installed VMWare, now windows 2003 is reporting multiple network cards...

All VMWare cards are disabeled.

MC Library Server is binding to IP 0.0.0.0 making it useless...

Need to force MC to start Library server on 192.168.0.250

Thanks

DD

[XeWonder]

MC IS SERVING LIBRARY ON 0.0.0.0 WHEN YOU HAVE MORE THAN 1 NETWORK CARD.

NOTHING TO DO WITH VMWARE!

[JimH]

It appears to be a problem related to VMWare.  I believe you've said it worked otherwise.

[robydago]

MC Library Server is binding to IP 0.0.0.0 making it useless...

I don't know why you keep saying that binding to 0.0.0.0 makes MC uselsess.

Binding to 0.0.0.0 should make MC listens to any ip\nic (unless there's a bug or any other problem)

Run this in a command prompt:

Code: [Select]

netstat -an|findstr 0.0.0.0
and you'll find many microsoft services listening on 0.0.0.0

[XeWonder]

It started working... i really don't know why or how.

i did not even re-boot my 2003 machine...

... and you are correct, it's still on 0.0.0.0

Sorry about this...