Windows 2008 Server. Dual NICs, Correct Configuration required for Workgroup only.

hi team,

i wonder if can me step step config of dns on windows 2008 server dual nics without active directoyr. workgroup only.

here setup. rras, dhcp, dns roles installed

windows ip configuration

   host name . . . . . . . . . . . . : wbserver
   primary dns suffix  . . . . . . . :
   node type . . . . . . . . . . . . : hybrid
   ip routing enabled. . . . . . . . : yes
   wins proxy enabled. . . . . . . . : no

ethernet adapter external:

   connection-specific dns suffix  . :
   description . . . . . . . . . . . : intel(r) gigabit ct desktop adapter
   physical address. . . . . . . . . : 68-05-ca-etc..
   dhcp enabled. . . . . . . . . . . : no
   autoconfiguration enabled . . . . : yes
   link-local ipv6 address . . . . . : fe80::b818:e6cc:d47a:1d64%14(preferred)
   ipv4 address. . . . . . . . . . . : 192.168.1.10(preferred)
   subnet mask . . . . . . . . . . . : 255.255.255.0
   default gateway . . . . . . . . . : 192.168.1.254
   dns servers . . . . . . . . . . . : 208.67.222.222
                                       208.67.220.220
   netbios on tcpip. . . . . . . . : enabled

ethernet adapter internal:

   connection-specific dns suffix  . :
   description . . . . . . . . . . . : hp nc107i pcie gigabit server adapter #2
   physical address. . . . . . . . . : e8-39-35-etc....
   dhcp enabled. . . . . . . . . . . : no
   autoconfiguration enabled . . . . : yes
   link-local ipv6 address . . . . . : fe80::a468:55b6:ccd1:bccb%12(preferred)
   ipv4 address. . . . . . . . . . . : 192.168.16.2(preferred)
   subnet mask . . . . . . . . . . . : 255.255.255.0
   default gateway . . . . . . . . . :
   dns servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1   <------what's this???
   netbios on tcpip. . . . . . . . : enabled

on client machine dchp settings gives:-

windows ip configuration

        host name . . . . . . . . . . . . : watchbatteryhp4
        primary dns suffix  . . . . . . . :
        node type . . . . . . . . . . . . : hybrid
        ip routing enabled. . . . . . . . : no
        wins proxy enabled. . . . . . . . : no
        dns suffix search list. . . . . . : wbdomain.local

ethernet adapter local area connection:

        connection-specific dns suffix  . : wbdomain.local
        description . . . . . . . . . . . : broadcom netxtreme gigabit
        physical address. . . . . . . . . : 00-13-21-etc....
        dhcp enabled. . . . . . . . . . . : yes
        autoconfiguration enabled . . . . : yes
        ip address. . . . . . . . . . . . : 192.168.16.4
        subnet mask . . . . . . . . . . . : 255.255.255.0
        default gateway . . . . . . . . . : 192.168.16.2
        dhcp server . . . . . . . . . . . : 192.168.16.2
        dns servers . . . . . . . . . . . : 192.168.16.2
        primary wins server . . . . . . . : 192.168.16.2
        lease obtained. . . . . . . . . . : 10 may 2012 18:34:24
        lease expires . . . . . . . . . . : 18 may 2012 18:34:24

first off seems work couple of times internal users cannot internet because cannot resolve domain names. stopping , restarting dns seems clear (i think!)

the dns logs give warning using single name label (wbserver) instead of domain name (wbdomain.local example).

what should correct dchp 015 dns domain name scope set if machines members of workgroup watchbattery? created wbdomain.local because that's used have set when had sbs2003 (which in domain).

the internal machines members of workgroup watchbattery server.

i not want load active directory , understand should work without.

do need set forward lookup zones in dns , if so, should put in there?

ad<thanks>vance

i have simmilar or more complex version of routing ),

in case shouldn`t problem configure.

let`s see structure, if understood correctly:

question why need ad? way, work

in expirience peferer give lan2 - 1-first ip ( *.*.*.1 ) ex. 192.168.16.1

so config works 100%:

srv1 ( dhcp,rras,dns):

lan1.srv1 - 192.168.1.254 ( ip,gate,dns )

nat ( includes both adapters )

lan2.srv1 - 192.168.16.1 ( no gate, no dns )

dhcp - scope ( 192.168.16.2-192.168.16.250 ) dhcp settings clients ( gate=192.168.16.1, dns=192.168.16.1 )

dns - forwarders(208.67.222.222) ( internat ws1..ws10 dns outsite ), zone - ( srv2.local = 192.168.16.s2 )

the moment - internal ad have dhcp , dns installed ( can ignore them )

ws1,ws2,ws3... - dhcp ( ip,gate,dns )

srv2 - ( static - 192.168.16.s2 ) gate(if srv2 want internet )=192.168.16.1 dns=127.0.0.1(forward 192.168.16.1)

check list:

srv1 -

open firewall tests

nslookup ya.ru (ok)

nslookup ya.ru 127.0.0.1(ok) - if not - dns on srv1 cannot higer dns - check dns.service settings in mmc

ws1-

ping 192.168.16.1(ok)

nslookup srv2.local 192.168.16.1 (ok)

nslookup srv2.local(ok) - if not check dhcpsrv,ip,gate,dns - aplied dhcp srv1 on lan1.ws1

srv2, if want internet here , check if dns on lan1.srv2 - set 127.0.0.1 , can thow in next dns (192.168.16.1)

it should work perfect!

actually srv1 - router firewall, make work simple possible ( use dlink...linksys @ home - connect , works)

but have other worstations or servers on net - conflicting it.

check computer connected in net - getting dhcp lan2.srv1 (192.168.16.1)

also rras.srv1 - tricky thing, try resetup it, carefull settings))) other wise router not nat )) , internal computers seen in same network 192.168.1.x

Windows Server  >  Network Infrastructure Servers