However, when I set the Lan connection property to use a fixed IP address,
the internet connection does not work. If I change it back to Obtain
address automatically, it works fine.... what to do ?
I am assuming that you are using DHCP from a router.
In the DHCP setting on your router you can usually give certain MAC
addresses (from the network card) to have a particular IP address assigned.
You are probably trying to set an internal IP address in the wrong range for
your router.
ss.
-Frank
"Rob" <rwc...@comcast.net> wrote in message
news:9M2dncQw_K6IFgDZ...@comcast.com...
What, exactly, are you trying to do? Who or what does this server serve?
I agree with "the literature" in general terms, but if you're setting this
server up to play with and learn how servers and networks operate then it
might not be so important - don't worry too much about leaving it on
automatic configuration for now.
If you're setting this up to provide a service for a business then I would
be worried; without wishing to sound disrespectful, the server setup for
this kind of thing needs to be in the hands of someone who understands how
to configure a network..
--
--
Rob Moir, Microsoft MVP for Security
Blog Site - http://www.robertmoir.com
Virtual PC 2004 FAQ - http://www.robertmoir.co.uk/win/VirtualPC2004FAQ.html
I'm always surprised at "professionals" who STILL have to be asked:
"Have you checked (event viewer / syslog)".
I am trying to set-up a home network and see some some of my "learning" in
action...
Previous responders were correct in that I have a cable modem and am using a
DLink router (which also serves as s DHCP server by handing out IP
addresses).
I want to see DHCP from a Windows 2003 server perspective pass out IP
addresses in the range I specified. It appears that I cannot have the best
of both worlds (if I specify a fixed IP address in my TCP/IP settings then I
cannot access the internet from that server).
Ultimately I want to...
- Set up a "test only" web server.
- Access my server and connected workstations securely via terminal services
- Implement AD / DNS/ DHCP from a testing standpoint
Thanks !
"Robert Moir" <robspamtr...@gmail.com> wrote in message
news:ejLIhV%23lGH...@TK2MSFTNGP05.phx.gbl...
This article may also help.
http://support.microsoft.com/kb/291382
--
Regards,
Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
> 127.0.0.1 if this server is also the DNS role.
never use the Loopback-Adress (127.0.0.1).
Everytime use the real IP-Adress.
--
Regards from Mainz/Germany
Yusuf Dikmenoglu
External fixed IP's are needed only if the server/network must be
accessed from an external source
Regards,
Hank Arnold
Regards,
Hank Arnold
Rob wrote:
> Yes, I am in learning mode....
>
> I am trying to set-up a home network and see some some of my "learning" in
> action...
> Previous responders were correct in that I have a cable modem and am using a
> DLink router (which also serves as s DHCP server by handing out IP
> addresses).
You should be able to assign a fixed IP address to a computer connected
to the DLink router as long as it is in the range as set on the router.
I've done it several times to resolve performance problems with a NIC.
It's usually done on the local computer network connection.
>
> I want to see DHCP from a Windows 2003 server perspective pass out IP
> addresses in the range I specified. It appears that I cannot have the best
> of both worlds (if I specify a fixed IP address in my TCP/IP settings then I
> cannot access the internet from that server).
If you want the Windows 2003 server issue DHCP addresses, you will have
to disable the DHCP server in the router.
>
> Ultimately I want to...
> - Set up a "test only" web server.
> - Access my server and connected workstations securely via terminal services
> - Implement AD / DNS/ DHCP from a testing standpoint
This will be fine as long as you are talking about testing internal to
your network. If, however, you want to access things from the Internet,
your problem will be that you probably have a Dynamic IP addresses. This
means that the address of your modem connection will change at the whim
of your ISP. You *could* manage it by monitoring the IP address and
adjusting any access from the Internet. However, a fixed IP connection
(more $$) will eliminate this problem.
BTW, you *DO* have a good, solid firewall software installed on your
computers, don't you? Don't count on the XP/2003 firewalls.