DaveDXB
My boss isreally givingme a headache these days...sometimes he connects....itgoes well for a month or two..and then some days he complains he cant connect....i just beleive the guy is messing with his laptop, but i still would like to know how MAC work in connecting to a Windows Server 2003 computer running as a Domain.
1- MY bosses laptop is running Tiger X
2- The user name and password on his laptop is = to username and password on windows server active directory.
3- last time he scanned the network and found it....
4- now he can find it =/
someone please give me a small course abt this.
Liban
Can't create an artificial Mac adress?
DaveDXB
MAC as in the OPERATING SYSTEM mac , the Apple
MaaaD
A64Venice
- Liban wrote:
Can't create an artificial Mac adress?
Liban is also a techie... :shock:
shinydiscoballs
In "Finder" (click on the desktop) click command-k (command is the one with an apple logo and pretzel on it). This pops up the "connect to server" dialogue. In here type the URL for the share you want to access, e.g.
smb://fqdn_for_server/share/
Note that windows notations of \\server\share will not work, it has to be in Internet URL format, it's largely a \ for / swap, but you'll need to use the FQDN for the server and not a WINS hostname. Having working DNS is crucial.. although in theory that's statements' correct for AD too.
You can go a lot further and fully integrate Tiger with AD for authentication if you want, but as long as the users shortname in OSX (e.g. jdoe might be the shortname for "John Doe") and password match their equivalents in Windows it should all just work. If they don't.. you can change the OSX shortname in the NetInfo Manager but that's getting a little complex if you don't know OSX - the "idiot's guide" books are a good start if you're a windows person.
Once you get it working have a look at for a CLI preference that will stop your boss littering the windows fileserver with .DS_Store meta-data files. The site is also useful for bug info and hints on Mac integration with Windows networks. The bugs are usually with Windows I might add..
SDB
DaveDXB
Exellent.
Thankyou very much for ur reply. Thats one thing new learnt for today.
I was able to get a connection with the server's shared folder, EXCEPT, it asked me for a user name and password. That where i kept getting stuck with the error message of wrong username and password although i use the same.
So im still fidling with it, lets see how it goes.
Thank very much 4 ur post. It truely helped.
DaveDXB
I giv up...i tried n tried
keeps giving me that darn user name and password. and i am 200% i used the same for both!
and i tried all combinations
Domain: IP address
Domain: FQDN
Domain: Computer Name . FQDN
username: caps
username: lowecase
password: password
wudnt connect.
^ian^
- DaveDXB wrote:
I giv up...i tried n tried
wudnt connect.
Suspect it might be a problem with encrypted passwords.
Try this for tips
DaveDXB
Thnks IAN, ill have to look into it and let u know what happens then.
1 Dubai Jobs .com The First Place to Find a Job in Dubai
DaveDXB
Warning: If you configure your computer to allow connections to Samba
or Windows (SMB/CIFS) servers using plain text passwords, when you
attempt to make any connection to such a Samba or Windows (SMB/CIFS)
server, your password will be sent "in the clear". This means that it
is possible for someone who is monitoring your connection to see your
password. This could lead to someone compromising the Samba or Windows
(SMB/CIFS) server. We strongly recommend that you configure your Samba
or Windows (SMB/CIFS) servers to exclusively use encrypted passwords.
Follow the steps below to configure your computer to use plain text
passwords to make SMB/CIFS connections when the specified Samba or
Windows (SMB/CIFS) server does not support encrypted passwords. (You
must be an administrator to do these steps.)
1. Make sure that you are not currently connected to any Samba or
Windows (SMB/CIFS) servers and that you do not have any Samba or
Windows-related error messages open.
2. Open the Terminal (/Applications/Utilities/).
3. At the prompt, type: sudo pico /etc/nsmb.conf
4. Press Return.
5. Enter your password when prompted, then press Return again.
6. You should see an empty file and a "New File" notice at the bottom
of the pico window. If you do not see the "New File" notice, this file
already exists.
7. Enter the following into the file so that it appears as follows:
8. [default]
9. minauth=none
10.
11. Save the file (press Control-O), press Return, then exit pico
(Control-X).
12. Type: sudo chmod a+r /etc/nsmb.conf
13. Press Return.
14. Restart your computer.
------------------------------------------------------
i tried this, still stuck :(
sometimes unix is really a headache, actually i take that back....most of the time it is.