Missing SpiceWorld right now...

@dbeato Crazy huh but thankful for the suggestion.

Thanks for the tips over the weekend...I am about to tackle this now...

• Yes, both the NAS and Server 2012 R2 have been rebooted.

• I just tried the FQDN of \archives.server.local and it takes me to the same login prompt that doesn't authenticate:
  

• This only happens with the fileshare as the WebGui for the synology works fine.

• It is on the domain. And users have rights to view it (only myself and a few others have write access)...those rights and permissions work fine if we get to the fileshare via \ipaddress
  

• SMB Is enabled. Here are the Min/Max settings:
  

I save this for for last because it is resolved now...there were time discrepancies on both file server and Synology NAS that didn't seem to affect any other system here at work...I fixed them borth and file share is working now...

Always the simplest right?

I have Synology NAS we use for Archiving and all of a sudden it no longer let's you get to it from the DNS name in file explorer... it has a simple address: \archives\ ... but it just stopped working...you can still ping the DNS name (archives) and go to the web GUI at http://archives . But the file share ONLY works via the IP Address.

If you try to go to \archives\ you are met with this...

And you can't authenticate...but if you use the IP Address (\\IPADDRESS), it works fine and can get to the share...

Our DNS/DHCP is Windows Server 2012 R2 based...

It has been driving me batty but I'm sure it is an easy fix but can't seem to find it.

Craziest thing...that program called CONFIG TOOL just decided to discover everything...was able to find cameras, give them a proper IP, used the IP of the network card on the Milestone system as GATEWAY address and I am halfway through this converstion now...

Thinking aloud, I wonder if the former camera PC had some kind of simple DHCP on it...I still have it powered on but can't seem to find anything that would serve as one.

@scotth So same as the private network or the domain network?

It is odd that it only finds the original 10 cameras and nothing that I add, even if adding to the original switch in the shop.

@Dashrender

This was in place before I got here and as far as I can tell, no..I tried a DHCP explorer selecting the private network card and it didn't find anything....unless it is the original switch in the shop but it is an unmanaged switch...the network card for the camera network shows this...

I duplicated that on the new PC's second network card and it sees the original 10 cameras but nothing I try to add. I'm sure this is easy but the solution doesn't present itself yet.

The Logan's Run TV SERIES...short run, low production values but good stories.

I convinced management to combine all of our IP Cameras into one single Milestone system. We have about 10 cameras on Milestone and 26 Amcrest Cameras across 5 DVRs. Before this, I tested two of our existing IP Cameras (Amcrest) on the current Milestone system and they were discovered and worked perfectly.

I migrated the old system into the new PC and it is working. It found all the existing cameras on the previous Milestone system. So, I am starting to bring in the Amcrest IP Cameras (Again, they worked during testing) and running into a few issues.

Just to preface, I am a Jack of all IT Trades but not an expert in networking.

First off, the existing Milestone Cameras are in a machine shop and they call come to a PoE switch in the shop and back into the office in a single cable to the Milestone system on a 192 network. I put that cable into another PoE switch with another one leading back to the Milestone system and it works great and sees all the existing Milestone cameras we had before.

The first Amcrest system I want to bring in has 4 cables into my server room. I plugged them into that PoE switch, went back into Milestone and scanned for them and it didn't find them. So using this IP camera called CONFIG TOOL,. I tried plugging them into another PoE switch with my laptop and still couldn't find them.

I went back into the Amcrest DVR and these cameras grabbed 10.1.1 addresses, assuming assigned by the DVR. I tried changing it to a 192 but it required a default Gateway and usually don't use one for 192.

So I am kind of stuck right now...I do believe if I can get these 4 cameras from 10.1.1 to a 192 address, then I should be able to plug into that switch and have Milestone find them, correct? And am I doing the Config Tool testing backwards?