Dhcp scope 192.168.0.10-192.168.0.254

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

Yes it is,

Dave

 

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

Sounds like a DNS issue.

Presumably you've not been messing around with the HOSTS file on the client? DNS is installed properly on the DC?

Just scrap it and start again imo. You shouldn't have any issues really.

Qs

 

If you can't ping by IP to an address on the same subnet you have some networking issues rather than being DNS, adding this to the fact you can't pick up a DHCP address.

 

When you say scrap it shall I reinstall the client or the server? As I have just recently installed this server?

Regards,

 

He didn't say he was pinging by IP.

Something is set up strangely so the best thing to do would be to start from scratch.

Remove all the server roles, reset all the network settings on both server and client and try again from scratch using the guide I posted earlier.

Qs

 

ok will do, I had it all working the first time I done it. But then something went wrong So I uninstalled all roles and then reinstalled and now still couldn't get it to work. I will try and do it again.

Thanks for everyones help,

Dave

 

You asked him to and he replied no.

beaumont, can you confirm whether or not you can ping by IP.

 

I cannot ping by using IP either.

Regards,

 

He actually didn't respond with what he pinged. People's responses can be confusing - for instance he didn't know the IP of the server, just as you asked him if it was a virtual environment, even after he had confirmed it was! (VM stands for Virtual Machine btw )

Easiest way forward is to scrap it as it will only take a couple of mins to do, and following the guide as I have already stated is the best way forward.

No point in messing about with it, it's better to understand it from step one.

Qs

 

Just scrap it and try again, because now you've shown it's not DNS then it's more than likely down to network connectvity - and because it's in a virtual environment even daniel can't help you

Scrap it, use the guide I posted and try it again

The best of luck matey.

Qs

 

Ok mate thanks will do, I've just got one more thing I can think of, Sytem restore to when it was connected to the domain and then try pinging.

Thanks for your helps both Q's and Daniel

Really appreciate it,

Thanks
Dave

 

Qs, are you deliberately being arsey?

 

No? :s

No worries mate, glad we could help.

Qs

 

well several of your comments say otherwise.

Beaumont, I trust you are doing this as a learning exercise, therefore I would carry on trying to fix it if you have the time. You never know when the info gained may come in handy.

 

right, I've fixed it. The virtual machine network connection was set to local network connection. (Which I dont know why as I didnt do it) But anyway I've changed it back to Wireless and it works fine now. Same for the server pc. Thanks everyone for your help.

Dave

 

Yeah mate I have done it now, it was a learning exercise and I've only used server for like 3 days lol. Thanks for both of your help.

Really appreciated.

Dave

 

Yeah all done now, after a sytem restore to when it was connected to the domain I thought I would try and leave the domain and see if the credentials you need to enter to leave a domain worked then I could find out if the conection the server was Local so I typed in domainadmin courtesy of q's link which I never knew has administrator privileges. Then it left the Domain so I thought it must of been something to do with virtual pc and then I changed it. Now it works fine. All of this just for that. But least it's sorted now, thanks,

Dave

 

Glad the guide helped.

'Local Only' is advised when doing lab work (as you then effectively seal off a small little network for testing). Try and get in the habit of setting this before doing any excercises as 'Local Only' isn't the default selection for network adapter type in Virtual PC.

Glad you're back up and running

Qs

 

Ok mate thanks again will do thanks again,

Dave