why sync clocks to share files without a domain

tremmor

tremmor

Well-Known Member
Im confused and just trying to get some basic answers.
i had enough problems with sharing with windows 7, XP-pro and XP home edition. i seen other people reply at microsoft and could not share. went through the steps and could not share. joined the workgroups, computername, shared files. someone replied you might only need to sync the clocks on the network to share files. others replied that fixed it.
is this a joke or what? what does syncing the clocks without domain have to do with sharing files on the home network?

http://www.microsoft.com/resources/.../en-us/windows_date_it_overview.mspx?mfr=true
 
Last edited:
Only if you are running Kerberos. Kerberos is a date/time sensitive ticketing system that allows for single sign on for your enterprise. So, lets say User A logs into their domain account. The sys admin has done some work and given User A access to the business share, the collaboration share, the development team share and the management share. Each of these shares is protected with permissions and ACLs, but are all part of a kerberized domain system.

So, once User A logs in, that user is issued a ticket, and that ticket offers as authentication to all their shares, that way User A doesn't need to put his credentials in every time they want to map a network share. The ticket must be in sync with the server because it will expire and the server doesn't allow mismatching tickets for security reasons, that way you can't spoof your own ticket.

Kerberos, as I understand it, allows for up to 4 minutes in variance between server and client for a ticket. Tickets also expire and a new one will be issued if still logged in. When User A logs out, their ticket is destroyed, so if User B logs into the same computer after User A, User B will not have access to any of User A's network shares.
 
Gow Dang.
Don't have a clue what your talking about. Good job though.
I think i will just let this one go. sounds like i don't need it. and not my concern.
thankyou for the explanation.
what ever it meant. Still the tech on this subject though.
tremmor
 
the reason i brought this up is because i setup sharing for printer from a laptop. its an Asus Eee. has Home XP on it. the workgroup is right and names are right on the other computer. im sharing my Windows 7 Pro with the other computers with XP pro just fine. I can share the network and access the other computers just fine including the printer and sharing both ways. (upload and download) like for favorite utilities, family pictures etc.
I can share the printer with windows 7 pro. i cannot access the Asus Eee with xp home edition. that laptop cannot see windows 7 pro directorys and from windows 7 pro or the others computers with xp pro can see the laptop Asus Eee xp home edition.
any thoughts or something else to try.
im starting to think it can't be done with the home edition.
thanks...........
 
It probably has to do with the added securities in Vista and 7 in SMB. You may have to set the network security policy to accept legacy (non NTMLv2) connections.

If you google how to edit the secpol.msc file in Windows 7 you should be able to find your answer.
 
You must log in or register to reply here.
Back
Top