M
Mark
Hi,
I am in a university department, and we want to map some network drives
across the local departmental network. I have done this by identifying
the computers whose drives are to be mapped via ip addresses.
The problem is that the department has run out of fixed ip addresses, so
the computers need to remain dynamic. This means that the networked
drives work fine as long as they aren't turned off for more than 24
hours. However, if they are, then they will likely be given new ip
addresses and this will break the network drives.
Is there a way to network drives using dynamic ip addresses, or some way
to update the ip addresses automatically if they do get changed? Is
there another way to map the network drives that will avoid this problem?
I am in a university department, and we want to map some network drives
across the local departmental network. I have done this by identifying
the computers whose drives are to be mapped via ip addresses.
The problem is that the department has run out of fixed ip addresses, so
the computers need to remain dynamic. This means that the networked
drives work fine as long as they aren't turned off for more than 24
hours. However, if they are, then they will likely be given new ip
addresses and this will break the network drives.
Is there a way to network drives using dynamic ip addresses, or some way
to update the ip addresses automatically if they do get changed? Is
there another way to map the network drives that will avoid this problem?