• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Internal Domain Naming Convention

Quite an old technet article talks about this http://technet.microsoft.com/en-us/library/cc708159(WS.10).aspx - in particular this paragraph is interesting. The link takes you to a document that shows how to reconfigure the Mac to work.

If you have Macintosh client computers that are running the Macintosh OS X version 10.3 operating system or later, and you are using the .local label for the full DNS name of your internal domain, then those client computers cannot discover other computers that are members of the network and that use the .local label. Macintosh OS X version 10.3 uses the .local label for its Rendezvous service. To work around this, it is recommended that you do not use the .local label for the full DNS name of your internal domain. If you must use the .local label, then you must also configure settings on the Macintosh computers so they can discover other computers on the network. For more information about how to configure client computers running Macintosh OS X version 10.3 or later, see “Connecting Macintosh Computers to a Windows Small Business Server 2003 Network” on the Microsoft Web site at http://go.microsoft.com/fwlink/?LinkID=39689.
 
haileris said:
Quite an old technet article talks about this http://technet.microsoft.com/en-us/library/cc708159(WS.10).aspx - in particular this paragraph is interesting. The link takes you to a document that shows how to reconfigure the Mac to work.

If you have Macintosh client computers that are running the Macintosh OS X version 10.3 operating system or later, and you are using the .local label for the full DNS name of your internal domain, then those client computers cannot discover other computers that are members of the network and that use the .local label. Macintosh OS X version 10.3 uses the .local label for its Rendezvous service. To work around this, it is recommended that you do not use the .local label for the full DNS name of your internal domain. If you must use the .local label, then you must also configure settings on the Macintosh computers so they can discover other computers on the network. For more information about how to configure client computers running Macintosh OS X version 10.3 or later, see “Connecting Macintosh Computers to a Windows Small Business Server 2003 Network” on the Microsoft Web site at http://go.microsoft.com/fwlink/?LinkID=39689.
Click to expand...

The document does provide good info. I only have one Mac at home, so it's not a big deal for me. It does see all SMB hosting devices on the network.

Edit: I will have to tinker with a few settings regarding SMB, so I do appreciate you posting the link.
 
Just checked - when I worked for an outsourcer (2nd biggest in the world at the time) on their NT4 retirement program, .local was the recommendation, so I guess there will be quite a few of these knocking around. :)
 
You must log in or register to reply here.
Back
Top