At work our director of IT and our network specialist both quit this week, leaving me, a trainee technician as the only member of the IT dept left. Among many things, I've hit one big problem, we have two offices, permanently linked by an 'isec tunnel' (?). we have two domains, one for each office, however we were in the process of joining them. We keep all our company files stored on a network drive in one of the offices, and usually everyone can access them, but after the it director left the network guy changed something to prevent him from accessing the network. Now everyone in the other office can't access the files, but the tunnel is still in place and their computers still show that they are connected to the other network.. what could be wrong and how do i fix it??
Access to network drives over a WAN
- Thread starter biocompanie
- Start date
- Status
thanks :wave:
yes, i have full control (and responsibility) for the entire company, not sure if i should be delighted or be running to the hills!!
yes, i have full control (and responsibility) for the entire company, not sure if i should be delighted or be running to the hills!!
tipstir
Posts: 2,873 +206
Are you the states? Too bad you got two opens I know some good staff would run over for these positions.
How far is the second office from your current location.. Do you have a tech there that can assist you? Otherwise you'll have to remote into those servers?
Could you explain more how your infrastructure is setup.. This type of problem should be solve by local engineers but you're the only one there right. To point you in the right directly will require more info from you.
How far is the second office from your current location.. Do you have a tech there that can assist you? Otherwise you'll have to remote into those servers?
Could you explain more how your infrastructure is setup.. This type of problem should be solve by local engineers but you're the only one there right. To point you in the right directly will require more info from you.
Based on what you are saying, there are several possibilities.
First thing I'd do is check that the trust relationship between the domains is still in place- If you want to be safe, just re-establish it.
Next, check your NTFS permissions and group memberships. Usually permissions will be assigned to files/folders by adding domain members to a global group. That global group is a member of a local group, and the local group is given permissions to the filesystem. Yeah, I know, seems backwards and stupid, but that is how MS recommends things when you're working across two domains in a forest. If you get rid of the second domain, things become much simpler.
Without knowing your setup and knowing what your network admin did, it's hard to speculate as to a fix. My first question would be what did he do. My next action would be a swift kick to his rump, and then ask why did he not just deactivate the user account, and change passwords on any privledged accounts that the ex-director may have known. No point in monkeying with settings (that I can see- there may be valid ones) when the goal is just to "escort someone out."
How do your users access the files? Do they have a drive mounted? Or do they access a share directly? What errors do they get? Are the errors when the users are browsing to files, or directly trying to access them?
I hope this helps somehow, or inspires an idea. If you can give us more info, though, perhaps we can help you iron a solution out.
PS- I'm looking for a new job right now too, if you're hiring
(ok, halfheartedly, but I am ready to leave my current position)
PSS- :wave: Welcome to Techspot!!! Hope you get your answers, and then stick around! :wave:
First thing I'd do is check that the trust relationship between the domains is still in place- If you want to be safe, just re-establish it.
Next, check your NTFS permissions and group memberships. Usually permissions will be assigned to files/folders by adding domain members to a global group. That global group is a member of a local group, and the local group is given permissions to the filesystem. Yeah, I know, seems backwards and stupid, but that is how MS recommends things when you're working across two domains in a forest. If you get rid of the second domain, things become much simpler.
Without knowing your setup and knowing what your network admin did, it's hard to speculate as to a fix. My first question would be what did he do. My next action would be a swift kick to his rump, and then ask why did he not just deactivate the user account, and change passwords on any privledged accounts that the ex-director may have known. No point in monkeying with settings (that I can see- there may be valid ones) when the goal is just to "escort someone out."
How do your users access the files? Do they have a drive mounted? Or do they access a share directly? What errors do they get? Are the errors when the users are browsing to files, or directly trying to access them?
I hope this helps somehow, or inspires an idea. If you can give us more info, though, perhaps we can help you iron a solution out.
PS- I'm looking for a new job right now too, if you're hiring
(ok, halfheartedly, but I am ready to leave my current position)PSS- :wave: Welcome to Techspot!!! Hope you get your answers, and then stick around! :wave:
- Status
Similar threads
