locked
windows server 2003 lab ip settings RRS feed

  • Question

  • Hi!

    I am setting up a windows server 2003 in a local lab - ethernet. What IP settings can i use

    i have tried 192.168.1.1 ip adress server

    subnetmask:255.255.255.0

    gateway:192.168.1.50

    dns:192.168.0.1

     

    Wednesday, April 7, 2010 10:20 AM

Answers

  • Non-routable IPv4 address ranges are as follows:

    class a: 10.x.x.x

    class b: 172.16.x.x thorugh 172.32.x.x

    class c: 192.168.x.x

    You can further subnet those as you like/need/want without problem.

    - R

    • Proposed as answer by Randall Ellis Wednesday, April 7, 2010 8:09 PM
    • Marked as answer by Rubel Khan Sunday, April 18, 2010 8:44 PM
    Wednesday, April 7, 2010 1:08 PM

  • i have tried 192.168.1.1 ip adress server

    subnetmask:255.255.255.0

    gateway:192.168.1.50

    dns:192.168.0.1

     

    Randall is correct.

    Looking at your settings though, your DNS address is a non-route-able address outside you configured subnet.

    Meaning that although your specified subnet will work, you DNS will not.

     

    Try making your DNS server 192.168.1.x and you environment will start working.


    Jarad, Brisbane Australia
    • Proposed as answer by Brian_Jones Thursday, April 8, 2010 3:45 PM
    • Marked as answer by Rubel Khan Sunday, April 18, 2010 8:44 PM
    Thursday, April 8, 2010 6:06 AM

All replies

  • Non-routable IPv4 address ranges are as follows:

    class a: 10.x.x.x

    class b: 172.16.x.x thorugh 172.32.x.x

    class c: 192.168.x.x

    You can further subnet those as you like/need/want without problem.

    - R

    • Proposed as answer by Randall Ellis Wednesday, April 7, 2010 8:09 PM
    • Marked as answer by Rubel Khan Sunday, April 18, 2010 8:44 PM
    Wednesday, April 7, 2010 1:08 PM

  • i have tried 192.168.1.1 ip adress server

    subnetmask:255.255.255.0

    gateway:192.168.1.50

    dns:192.168.0.1

     

    Randall is correct.

    Looking at your settings though, your DNS address is a non-route-able address outside you configured subnet.

    Meaning that although your specified subnet will work, you DNS will not.

     

    Try making your DNS server 192.168.1.x and you environment will start working.


    Jarad, Brisbane Australia
    • Proposed as answer by Brian_Jones Thursday, April 8, 2010 3:45 PM
    • Marked as answer by Rubel Khan Sunday, April 18, 2010 8:44 PM
    Thursday, April 8, 2010 6:06 AM
  • It worked - thank you
    Monday, April 26, 2010 7:56 AM