Home Network Set-up Question

[EchoedTruth]

Originally Posted by Klendathu [You must be logged in to view images. Log in or Register.]

Most MS Server OS come out of the box with that shitty "MS Enhanced Internet Security" turned on. In 2008 R2, I think you turn it off by going into Server Manager Console, that annoying page that pops up on each administrator login (that you probably disabled after startup by now). It's a good idea to turn off enhanced security, cause then you can install things from network locations, which make life easier, especially in the sandbox.

Also, until you run dcpromo and start using R2 for DHCP\DNS, you need to point it to your Netgear for DNS, in the same spot where you set up the static IP for it. Let us know if that helps.

True test of connectivity - ping something outside of your router. Like www.google.com.

Well it works fine until I assign a static IP to the laptop using the IPv4 properties. I entered the right gateway, subnet mask, and IP I had reserved on the router. Still wouldn't connect. As soon as I set it to the "automatically receive IP from..." setting then it works again.

I've disabled enhanced security. I'm still fuzzy on how the DNS/DHCP thing works. I wouldn't think I'd need to run/enable those to connect via a static IP though...

[timhutton]

Don't do this shit with physical boxes, use VMs.

Honestly, just spend like $800 buy some hardware, install esxi and make your own virtual infrastructure shit isn't that hard or expensive and you will learn a ton/have fun.

[radditsu]

Originally Posted by timhutton [You must be logged in to view images. Log in or Register.]

Don't do this shit with physical boxes, use VMs.

Honestly, just spend like $800 buy some hardware, install esxi and make your own virtual infrastructure shit isn't that hard or expensive and you will learn a ton/have fun.

Shit I ran 4 vm 2008 for my microsoft certs with my desktop and 180 day trials and pirate vmware. Needed 0 dollars

[Klendathu]

hmmm, run ipconfig/all form a command prompt and see what your Netgear is giving you for IP settings. It may give a clue as to why the static setup is not working.

Maybe try and go low on the static IP. Set the DHCP range to be 10-235, and make your server .5 or something less than .11. Home routers are not known for being extremely flexible, dont be surprised when you find out the weak link in the chain is your Netgear.

Or you could commit to the process all at once, turn off everything on your router but the firewall, promote your server, establish a domain, set your DHCP and DNS up on it, and start having everything on your network refer to it. This is where you're going to end up sooner or later.

[EchoedTruth]

Originally Posted by Klendathu [You must be logged in to view images. Log in or Register.]

hmmm, run ipconfig/all form a command prompt and see what your Netgear is giving you for IP settings. It may give a clue as to why the static setup is not working.

Maybe try and go low on the static IP. Set the DHCP range to be 10-235, and make your server .5 or something less than .11. Home routers are not known for being extremely flexible, dont be surprised when you find out the weak link in the chain is your Netgear.

Or you could commit to the process all at once, turn off everything on your router but the firewall, promote your server, establish a domain, set your DHCP and DNS up on it, and start having everything on your network refer to it. This is where you're going to end up sooner or later.

Good idea, I'll try that out. I appreciate it [You must be logged in to view images. Log in or Register.]
The problem is that my "server" is just an old hp laptop that sounds like a jet turbine when running. I don't want my network tied to that.

[radditsu]

Did you set the default gateway to the router ip? Also setup dns forwarders in your active directory server to your isp dns settings or a google public dns. It will fix any resolution errors your ad server can't fix.