IMS3000 browser connect issue

[Scott Hardin]

Greetings and many thanks,

I solved IMS3000 browser timeout and content delete issues from reading prior posts, …but I still have a browser connect issue (with a different computer):

• Single screen, no TMS used, IMS3000 server v3.5.13 (using eth0) and NC3541L projector plugged into 1000Mbps network switch not connected to the internet.
• Only 1 browser logged in at a time, currently a Win7 laptop w/ Win7 compatible version of Chrome plugged in to the network switch
• Trying to change over to Win11 desktop (…disconnected the Win7 laptop) but
  • Same URL address I typed in before with Win7 now shows "Site can't be reached" error
  • Can't view IMS3000 log on screen by typing in 192.168.1.129
  • Can't view NEC Basic Control screen by typing in 192.168.1.134
• Different browsers with Win11 give same result, whether latest Chrome v137.0.7151.69, Firefox, or Edge
  • Tried Chrome with Safe Browsing OFF, Secure DNS OFF
• Network switch LED's do glow green to indicate a 1000Mbps signal from the Win11 computer so I guess the NIC card and cable must be OK.
• Same error when plugging directly into the server or projector thus bypassing the network switch.

Sorry to bog you down with the following network details, but maybe I'm doing something stupid?

• In the (working) Win7 Network connections it shows up as Local Area Connection, Unidentified Network …then changes to Network 4 after booting the DCCv2 control app.
• In the (non-working) Win11 Network settings it shows up as "Ethernet Unidentified network," Intel Network Adapter I225-T1 with these details:
  • Media state: Enabled
  • Bytes sent: 123
  • Bytes received: 0
  • Link speed: 1000 Mbps
• And these properties
  • IP assignment: Automatic (DHCP)
  • DNS server assignment: Automatic (DHCP)
  • Link-local IPv6 address: (long address)
  • IPv6 DNS servers: (3 different Unencrypted entries)
    • I think I chose something about IPv4 in Chrome but I'm not at work presently to check.
    • But aren't IPv6 addresses backwards compatible with IPv4?
• "Ethernet 2 Not connected" also shows up for some reason, even though there's only one NIC card …but it does say "not connected."
• Windows Network Troubleshooter didn't help.

Thanks for any thoughts you might have.

[Frank Cox]

ping 192.168.1.129
ping 192.168.1.134

If you can't connect then it's a connection issue and not a browser issue.

If you do get a response, then it's a browser issue.

[Rajendran Paranthaman]

Hi

Possible means try these ip

Keep modern ip as 192.168.1.130

Projector ip as 192.168.1.128
Ims 3000 ip as 192 .168 .1.129

It will connect easy I think so my friend


Thanks

[Leo Enticknap]

If you've replaced the PC, then the new PC's network interface controller (NIC) will need to be configured with an IPv4 address and subnet mask that enables it to communicate with the equipment in the booth. You state that it is currently set to DHCP (Dynamic Host Control Protocol - a system whereby a computer will ask a server on the local network to give it an IP address). If there is no DHCP server on the projection LAN (e.g. a gateway/router), or if there is but it is giving you an address not in the 192.168.1.XXX subnet, that's your problem. The solution is to set a static address in that subnet, but not one that is held by any other device (using the one from the retired computer would be the safest bet). You can find tutorials online for doing this, or alternatively it might be worth bringing an IT tech in to do that, and check your local area network for issues more generally while he or she is at it.

Incidentally, if your IMS3000 is still on version 3.5.13, it will need to be updated to 3.5.20 or 3.21.7 by December 31 this year. If this isn't done, your IMS3000 will stop working at that point, and will not be repairable in the field (it would have to be returned to Dolby).

[Scott Hardin]

Thanks for the ping suggestion Frank, and the detailed network explanation Leo. I'll try that first chance I get, and we're scheduling a service call to update the Dolby to 3.21.7.

[Ryan Gallagher]

Everyone's response on network setup is likely the correct direction to look.

Either in "view network connections" or a windows command shell you can verify the IP you have set or have been given is on the same network and subnet etc.

pinging your destination IP is an easy test to see if you can see the destination. If you can't you can use "ipconfig" on the command line to see what IP your client machine has.

As Leo suggests, if there is no DHCP server on the projection network currently, you'll have to set a suitable static IP address/gateway/subnet mask, if you are retiring the win7 machine you can repurpose it's IP as one easy option, but they should NOT both be placed on the network going forward without giving the win7 machine a different available IP.

Everything in your booth is probably based on IPv4 addresses that look like your existing (eg 192.168.1.129), ignore the IPv6 stuff.

[Scott Hardin]

Solved - Thanks Ryan, and all the others. It entailed:

• going under the Win11 computer's TCP/IPv4 properties and assigning an Alternate Configuration similar to the working Win7 laptop, but
• varying the last digit of the IP address to not butt heads with the Win7 laptop should I want to use it as a backup.
• I think I finally bumped into the correct screen to set this on Win11 via …More adapter options.

This turned on a light in my creaky braincells from doing that years ago, when we started with a WinXP laptop and an NC2500 Series 1 in May of 2006, our first summer to use a Dolby DSS server which wasn't yet JPEG compatible. (We started with Chronicles of Narnia in mpeg Digital Cinema.)

This is an historical multi-purpose venue in Atlanta (Fox Theatre) that finds me working backstage on far more Broadway shows than in the booth for movies now but it was a movie palace in its heyday. Heck, I started back in '78 when it was carbon arc and changeovers for many years, but I'll save all that for a separate post someday.

[Ryan Gallagher]

Solved - Thanks Ryan, and all the others. It entailed:

Glad to help a sister venue out. The Fox is a stunningly gorgeous theatre. Hello Local 927!

The warehouse photo gallery has no photos of your booth! Would love to view another historic projection booth.

[Ed Gordon]

Glad to help a sister venue out. The Fox is a stunningly gorgeous theatre. Hello Local 927!

The warehouse photo gallery has no photos of your booth! Would love to view another historic projection booth.

See:

https://cinematreasures.org/theaters/85/photos

https://www.pbs.org/video/georgia-pu...s-fox-theater/

[Ioannis Syrogiannis]

The IP scheme of the server and projector seems to be remnant of the DSS era, kept the same upon upgrade, maybe for the sake of the cinema processor and automation. The network mask on those is blocking the first 128 numbers of the last octet (255.255.255.128). That is, if the network scheme was kept intact. Therefore, if your laptop IP was something like 192.168.1.20, they wouldn't play along well.
You could as well check the subnet mask used on the system of devices and change it, to give you more "room" for connected devices. (Or not. )

[Scott Hardin]

Ryan,

I guess I should add a few pictures to the gallery then ...still working my way around the forum slowly.
I see that Ed added some still and video links to the Fox as well ...amazing, and I appreciate the extra explanations from Ioannis.

I'll touch back later.