January 23, 20251 yr Hello, My server name has been changed to its name-2 on my router and I can access it with name-2.local instead of name.local. Ip address still working normaly. Anyone has already experienced that? I have a cor api notification so I added the new origin in the connect menu. I think it comes from the router but everyone on the web people are saying it is the machine which declares itself to the router so I dont understand. Thank you for your help.
January 23, 20251 yr Community Expert Do you have an entry in the static routes on your router for 'name' and what is the MAC address for that assignment? Compare that MAC address to to one for the NIC in your server. (All computer "names" must be unique on the LAN or things usually don't work right.)
January 23, 20251 yr Author Here are some screenshot of the settings on the router and the server. The mac is the same. I dont know where he got that veda-2 name from seriously. Edited January 23, 20251 yr by Daaadou
January 23, 20251 yr Author I forgot to mention something. When I looked at the address the first time, there were a netbios mdns address named veda and another one named veda-2. I suppressed the netbios ability in the smb section. No more netbios address in the router menu but he kept veda-2 for the server name.
January 23, 20251 yr Community Expert 1 minute ago, Daaadou said: I forgot to mention something. When I looked at the address the first time, there were a netbios mdns address named veda and another one named veda-2. I suppressed the netbios ability in the smb section. No more netbios address in the router menu but he kept veda-2 for the server name. Now see if you can rename "veda-2" on the router to "veda" . (You may want to read the router manual...) (You appear to be a native-speaking French person and my understanding of french is very, very limited as I try to figure things out from your screenshots.) Writing this reply to you before the Above post: (I hate to ask this question!) Is there another computer on the LAN named using just the letters veda (small, CAPITAL, or any combination of the two) in that order? ("Case" of the letters may be ignored by the router. This is an area of great confusion between Windows and UNIX/Linux and often causes problems.) You have made the IP address static on the server. Did you made it static on the router? (You appear to be a native-speaking French person and my french is very limited as I try to figure things out from your screenshots.)
January 23, 20251 yr Author 1 hour ago, Frank1940 said: Now see if you can rename "veda-2" on the router to "veda" . (You may want to read the router manual...) (You appear to be a native-speaking French person and my understanding of french is very, very limited as I try to figure things out from your screenshots.) Writing this reply to you before the Above post: (I hate to ask this question!) Is there another computer on the LAN named using just the letters veda (small, CAPITAL, or any combination of the two) in that order? ("Case" of the letters may be ignored by the router. This is an area of great confusion between Windows and UNIX/Linux and often causes problems.) You have made the IP address static on the server. Did you made it static on the router? (You appear to be a native-speaking French person and my french is very limited as I try to figure things out from your screenshots.) Thank you for your answer. Sorry for the screenshot in French. I just set my unraid as static on the router as well. Maybe I need to reboot devices. I did a factory reset on the router but it still sees it as veda-2.
January 23, 20251 yr Author Solution Ok I think I found it. I killed the two other smb option, wds and macos. Reboot, now I can access via veda.local. I Hope it stays that way. Thank you for your help Frank.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.