@Dashrender said:

I feel like I've asked this before, Scott, but why does RAID 1 need to do anything funky at all on the drive?

Assuming that most NASs today run some flavor of Linux, wouldn't they run a Linux compatible format, and therefore be readable in a Linux machine?

I suppose just to make things more difficult, the NAS could use a proprietary file system, or at the mimimum write something to the starting sectors tying it to the NAS to create artificial lock in. Am I missing something?

Thats what I was thinking - ie if we have a Linux compatible PC (mac) then we can read the data?

Just to add- they didnt plug in the OLD drives into the new Nas box...its completely separate. The new NAS is up and running on the network with new drives...We're left with 2 old NAS hard drives. Shall i tell them to plug it all back to how it was and see if we can view data on the nas?

We can access data whilst Old NAS is on but its 6 years old and the client (without telling us) ordered a new NAS, plugged in and configured it and then pulled drives out of old NAS (which is a ReadyNas 312) and were trying to copy the data from the old drive across to the new!!!

@scottalanmiller Thanks Scott...If I plug into a MAC will that work?
I heard about Paragon HFS+ - is this possible to use?

Please see image. We have a NAS box that was failing (raid 1 config).
We've taken the drive out and plugged into a PC .. as you can see from the image, DISK 1 is online and healthy, yet we cannot view its contents in Windows Explorer - I am unable to map a letter to the drive...I only have the options to delete volume or convert to dynamic disk.

We dont want to loose the data.

PS: We plugged in the second drive and had the same response.
Does anyone know how I can get this online so we can view its contents?

@Kelly said:

Here's a quick breakdown: http://serverfault.com/questions/12854/cidr-for-dummies. I was going to try to explain most of that, but they're hitting the high points.

thanks i'll look at this URL in more detail tomorrow

@scottalanmiller said:

A better starting point, IMHO, is the CompTIA Network+. It covers all of this well and is cheap. No need to take the exam, the Exam Cram book is allthat you need.

which book would you recommend?

I'd love to do the CCNA but thats too expensive and time consuming...I'd just like to learn the basics and understand the theory behind it...I've done a lot of reading and watched videos on it but it can go over my head so was hoping peeps on here could break it down simply and skim the basics....I appreciate theres too much to cover in a small paragraph.

Hi all

Maybe a stupid question but thats why I'm here... I typically support small networks between 1-50 users and have always used the IP subnet range 192.168.x.x / 24

I'm intrigued about using 10.0.x.x ranges or other subnets...Why would one use another range? I believe for security or bigger range but I'm clueless when it comes to subnetting and understanding the different net masks and getting my head around it hurts!!! So I guess the real question I'm asking is - can someone explain IP ranges and subnets in an dummy/idiot proof guide language and explain the benefits of using specific masks.

Thanks in advance

I havent worked with ADMT before but will look into it and if I'm capable of doing it and the time frames make sense, I'll go with it.....Otherwise when I have a spare weekend will probably nuke and start from scratch...Again if the main problem is ONLY that staff cant view their website internally then as far as I'm concerned this isnt a urgent problem that warrants immediate action. I'll create the DNS entries manually for the moment so hopefully it'll be okay for now...see the dns entired below, is this all I'll need to create (as well as the www record for the website)? Thanks again for your replies and responses.

I've never used or worked with Samba so dont know anything about it. The AD I thought was great for them as they want to have more 'control' over users, add more security to the network and manage permissions on folders much better. I'm familiar with AD so thought it would suit them well.

The reason we named the domain name the same as their external domain is because a Microsoft technician advised me to do so if we wanted to Sync our Office365 tenant with the on-premise server.

I can easily nuke the DC and start over, but to re-configure the 15 computers and drag everything over to their new profile is easy, but frustrating to have to spend the extra time doing it as i've just done it for their new server!!!

Not a lot in AD. Of course the usual such as users/groups, some group policies and file share permissions.

So for example in my DNS, I'd need to manually add the office 365 records, such as MX records, autodiscover CNames etc?

So for reference, the company is about 5 years old. They have 15 staff and growing (at reasonable pace) was mayhem to control users/passwords/group policies etc. Therefore having just joined the company myself, suggested getting some structure in place and to get the server...so yes, new server - established company.

PS - What settings do I need to do to get the active sync working? I did have this problem on a few computers...I couldn't understand why some worked and some didnt!! The ones that didnt, I changed DNS to Google and that helped autodiscover. then put it all back to DHCP. Which is why I questioned if emails will be okay in the initial post.

@scottalanmiller noted! lesson learned. thanks again

no mx records are present on our server at all.
I dont have a problem with the website not working internally (without the www). I'll see if i can convince them next week though! Thanks for your help.

Next time, i'll be sure to name it something other than the same domain name!!! sigh

If having to tell/train users to type www. in front of their domain name to view their own website internally is the biggest problem I'll face then it's probably not worth me renaming/reconfiguring it all over again then.

Would there not be any other implications/issue's i'll face down the line?
If our email system is on office365 am I safe in saying the emails wont have any issues or be affected?

Should I want to rename the domain name to be AD.domain.com is that a big task to do?

Hi all

I'm having a problem with a new client server 2012 R2 where the internal domain name is the same as the external domain eg. companyname.com for internal AD domain name, and their website and emails are also on companyname.com (note: emails are with office365)

Internally if I ping the domain name, it replies back with the internal IP address (192.168.0.2) which is our DNS and Domain Controller and staff are unable to browse to their website.

I have created a manual WWW entry in DNS Manager so now staff can now go to www.companyname.com and it resolved but without the www it doesnt work.

I noticed in our DNS manager, there is an entry that says:

(same as parent folder) - Host A - 192.168.0.2 - I believe this is causing the problem. If i remove it, it simply comes back shorlty after as this is the default A record for the DC.

Is it a problem to have the internal domain name the same as external or should I rename? Can i rename? what do you advise?
Sorry if this is badly written but I hope you understand the nature of the query. Let me know if any Q's

Thanks