IP address.

G

Guest

HI All,

Advice needed for static IP adress configuration on 3 PC's in order to
administer a legacy remote server.

I am assuming that i needs to be done is that we need an admin account with
access rights and the IP address range of the sight that is having the Static
IP addresses installed? In addition to that should the IP addressess be
reserved in DHCP?

The PC's are all XP builds.

Any advice would be greatly appreciated.

Kind Regards.
 
R

Rick Rogers

Hi Peter,
Advice needed for static IP adress configuration on 3 PC's in order to
administer a legacy remote server.

Ok, but you should be able to access it by name as well as IP if the access
is being done from within the lan.
I am assuming that i needs to be done is that we need an admin account
with
access rights
Yes.

and the IP address range of the sight [site] that is having the Static
IP addresses installed?
Yes.

In addition to that should the IP addressess be
reserved in DHCP?

Made available, the system should grab that particular IP when booted if
configured properly. I suggest setting it high enough into the available
range so that dynamically assigned systems don't pre-empt it. Also, if you
are accessing remotely from outside the LAN than you may also need to set
port forwarding up from outside to the internal IP of the target system.
Which port to be used is dependent on the client you are using to access
(eg: Windows' Remote Desktop uses 3380).

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Windows help - www.rickrogers.org
 
G

Guest

Thanks for you comment Rick....i will take them on board.

Kind Regards.
--
Peter


Rick Rogers said:
Hi Peter,
Advice needed for static IP adress configuration on 3 PC's in order to
administer a legacy remote server.

Ok, but you should be able to access it by name as well as IP if the access
is being done from within the lan.
I am assuming that i needs to be done is that we need an admin account
with
access rights
Yes.

and the IP address range of the sight [site] that is having the Static
IP addresses installed?
Yes.

In addition to that should the IP addressess be
reserved in DHCP?

Made available, the system should grab that particular IP when booted if
configured properly. I suggest setting it high enough into the available
range so that dynamically assigned systems don't pre-empt it. Also, if you
are accessing remotely from outside the LAN than you may also need to set
port forwarding up from outside to the internal IP of the target system.
Which port to be used is dependent on the client you are using to access
(eg: Windows' Remote Desktop uses 3380).

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Windows help - www.rickrogers.org
 
G

Guest

Hi Rick,

Could you answer one quick question please.

Not sure whether i understand what you are suggesting when you reply...to
the question "In addition to that should the IP addressess be
reserved in DHCP?"

You answered Made available, the system should grab that Particular IP when
booted if configured properly? Surely if it is configured as a static IP
address then why would it go looking for an IP address?

If you could explain i would be more than greatful.

--
Peter


Rick Rogers said:
Hi Peter,
Advice needed for static IP adress configuration on 3 PC's in order to
administer a legacy remote server.

Ok, but you should be able to access it by name as well as IP if the access
is being done from within the lan.
I am assuming that i needs to be done is that we need an admin account
with
access rights
Yes.

and the IP address range of the sight [site] that is having the Static
IP addresses installed?
Yes.

In addition to that should the IP addressess be
reserved in DHCP?

Made available, the system should grab that particular IP when booted if
configured properly. I suggest setting it high enough into the available
range so that dynamically assigned systems don't pre-empt it. Also, if you
are accessing remotely from outside the LAN than you may also need to set
port forwarding up from outside to the internal IP of the target system.
Which port to be used is dependent on the client you are using to access
(eg: Windows' Remote Desktop uses 3380).

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Windows help - www.rickrogers.org
 
R

Rick Rogers

Hi,

As long as it's in the available range, the system will boot with that IP
and work. If it's not available, the IP will still be assigned but will
work. But this is obvious. What I meant by the comment is that the system
will look to verify that the IP is useable when it attempts to connect.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Windows help - www.rickrogers.org

Peter F said:
Hi Rick,

Could you answer one quick question please.

Not sure whether i understand what you are suggesting when you reply...to
the question "In addition to that should the IP addressess be
reserved in DHCP?"

You answered Made available, the system should grab that Particular IP
when
booted if configured properly? Surely if it is configured as a static IP
address then why would it go looking for an IP address?

If you could explain i would be more than greatful.

--
Peter


Rick Rogers said:
Hi Peter,
Advice needed for static IP adress configuration on 3 PC's in order to
administer a legacy remote server.

Ok, but you should be able to access it by name as well as IP if the
access
is being done from within the lan.
I am assuming that i needs to be done is that we need an admin account
with
access rights
Yes.

and the IP address range of the sight [site] that is having the Static
IP addresses installed?
Yes.

In addition to that should the IP addressess be
reserved in DHCP?

Made available, the system should grab that particular IP when booted if
configured properly. I suggest setting it high enough into the available
range so that dynamically assigned systems don't pre-empt it. Also, if
you
are accessing remotely from outside the LAN than you may also need to set
port forwarding up from outside to the internal IP of the target system.
Which port to be used is dependent on the client you are using to access
(eg: Windows' Remote Desktop uses 3380).

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Windows help - www.rickrogers.org
 
G

Guest

Hi Rick,

Thanks very much for you comments. They are greatly appreciated.

Kind Rgs

--
Peter


Rick Rogers said:
Hi,

As long as it's in the available range, the system will boot with that IP
and work. If it's not available, the IP will still be assigned but will
work. But this is obvious. What I meant by the comment is that the system
will look to verify that the IP is useable when it attempts to connect.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Windows help - www.rickrogers.org

Peter F said:
Hi Rick,

Could you answer one quick question please.

Not sure whether i understand what you are suggesting when you reply...to
the question "In addition to that should the IP addressess be
reserved in DHCP?"

You answered Made available, the system should grab that Particular IP
when
booted if configured properly? Surely if it is configured as a static IP
address then why would it go looking for an IP address?

If you could explain i would be more than greatful.

--
Peter


Rick Rogers said:
Hi Peter,

Advice needed for static IP adress configuration on 3 PC's in order to
administer a legacy remote server.

Ok, but you should be able to access it by name as well as IP if the
access
is being done from within the lan.

I am assuming that i needs to be done is that we need an admin account
with
access rights

Yes.

and the IP address range of the sight [site] that is having the Static
IP addresses installed?

Yes.

In addition to that should the IP addressess be
reserved in DHCP?

Made available, the system should grab that particular IP when booted if
configured properly. I suggest setting it high enough into the available
range so that dynamically assigned systems don't pre-empt it. Also, if
you
are accessing remotely from outside the LAN than you may also need to set
port forwarding up from outside to the internal IP of the target system.
Which port to be used is dependent on the client you are using to access
(eg: Windows' Remote Desktop uses 3380).

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Windows help - www.rickrogers.org
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top