I have a remote system I need to connect to. Unfortunately, the last
tech did not change the IP to DHCP. So the system is on a
192.168.0.XXX address. The rest of the network is on 192.168.2.XXX. No
one is in the office right now, but that system is still on. Is there
any possible way to connect to that system so I can change it's IP?

Re: Wrong Network by Phillip

Phillip
Mon Apr 07 08:37:13 PDT 2008

If you are on the same Physical Segment (no router needs crossed) then go to
the TCP/IP Properties of the machine you are sitting at.

If it is a DHCP Client then reconfigure the machine with an static address
compatible with the target server. "Do you thing" and then set your machine
back to DHCP.

If it is a statically assigned machine,...from the TCP/IP Properties click
the Advanced button,...then the Add button under IP Addresses and add an IP#
(and maybe mask) that is compatible with the target server. "Do you thing"
and then set your machine back to the way it was.

You'll probably want to use Remote Desktop to make the adjustment on the
server. It will kick you off as soon as you make the change. You are
really better off to just get up,...walk over to where ever it is and fix it
manually.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

"nick" <cipher7836@gmail.com> wrote in message
news:e370c405-70cf-463d-93ac-866fba55f81a@n58g2000hsf.googlegroups.com...
>I have a remote system I need to connect to. Unfortunately, the last
> tech did not change the IP to DHCP. So the system is on a
> 192.168.0.XXX address. The rest of the network is on 192.168.2.XXX. No
> one is in the office right now, but that system is still on. Is there
> any possible way to connect to that system so I can change it's IP?



Re: Wrong Network by nick

nick
Mon Apr 07 09:23:30 PDT 2008

On Apr 7, 10:37=A0am, "Phillip Windell" <philwind...@hotmail.com> wrote:
> If you are on the same Physical Segment (no router needs crossed) then go =
to
> the TCP/IP Properties of the machine you are sitting at.
>
> If it is a DHCP Client then reconfigure the machine with an static address=

> compatible with the target server. =A0"Do you thing" and then set your mac=
hine
> back to DHCP.
>
> If it is a statically assigned machine,...from the TCP/IP Properties click=

> the Advanced button,...then the Add button under IP Addresses and add an I=
P#
> (and maybe mask) that is compatible with the target server. =A0"Do you thi=
ng"
> and then set your machine back to the way it was.
>
> You'll probably want to use Remote Desktop to make the adjustment on the
> server. =A0It will kick you off as soon as you make the change. =A0You are=

> really better off to just get up,...walk over to where ever it is and fix =
it
> manually.
>
> --
> Phillip Windellwww.wandtv.com
>
> The views expressed, are my own and not those of my employer, or Microsoft=
,
> or anyone else associated with me, including my cats.
> -----------------------------------------------------
>
> "nick" <cipher7...@gmail.com> wrote in message
>
> news:e370c405-70cf-463d-93ac-866fba55f81a@n58g2000hsf.googlegroups.com...
>
>
>
> >I have a remote system I need to connect to. Unfortunately, the last
> > tech did not change the IP to DHCP. So the system is on a
> > 192.168.0.XXX address. The rest of the network is on 192.168.2.XXX. No
> > one is in the office right now, but that system is still on. Is there
> > any possible way to connect to that system so I can change it's IP?- Hid=
e quoted text -
>
> - Show quoted text -

I guess I should've been more specific......

I'm connecting to the network remotely from VERY far away. Basically,
it's a home office that's on a little island about 4 hours north of
where I live. I set everything up when I was there, but they failed to
mention a system that was upstairs. No one will be back in until
Wednesday.

The router is on the 192.168.0.XXX network which is the network the
upstairs system is on. The other systems use that router as a gateway
to the Internet even though they are on the 192.168.2.XXX network. I
was hoping I could add a route to the 0.XXX network on (that the
upstairs computer is on) the computer I connect to from home. Then RDP
into the upstairs machine, and change it's IP. But that isn't working
out too well. The route command sees that the gateway is on another
network, and won't let me add a path.

Re: Wrong Network by goarilla

goarilla
Mon Apr 07 09:25:26 PDT 2008

nick wrote:
> I have a remote system I need to connect to. Unfortunately, the last
> tech did not change the IP to DHCP. So the system is on a
> 192.168.0.XXX address. The rest of the network is on 192.168.2.XXX. No
> one is in the office right now, but that system is still on. Is there
> any possible way to connect to that system so I can change it's IP?

if pinging works why wouldn't remote desktop work (if enabled offcorse)

Re: Wrong Network by Phillip

Phillip
Mon Apr 07 11:39:32 PDT 2008

You can't cross the router.
It will have to sit there till Wednesday.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

"nick" <cipher7836@gmail.com> wrote in message
news:9c2717e6-42c7-4246-aca3-56063d2dd9b8@p25g2000hsf.googlegroups.com...
I guess I should've been more specific......

I'm connecting to the network remotely from VERY far away. Basically,
it's a home office that's on a little island about 4 hours north of
where I live. I set everything up when I was there, but they failed to
mention a system that was upstairs. No one will be back in until
Wednesday.

The router is on the 192.168.0.XXX network which is the network the
upstairs system is on. The other systems use that router as a gateway
to the Internet even though they are on the 192.168.2.XXX network. I
was hoping I could add a route to the 0.XXX network on (that the
upstairs computer is on) the computer I connect to from home. Then RDP
into the upstairs machine, and change it's IP. But that isn't working
out too well. The route command sees that the gateway is on another
network, and won't let me add a path.



Re: Wrong Network by nick

nick
Mon Apr 07 16:06:40 PDT 2008

On Apr 7, 1:39=A0pm, "Phillip Windell" <philwind...@hotmail.com> wrote:
> You can't cross the router.
> It will have to sit there till Wednesday.
>
> --
> Phillip Windellwww.wandtv.com
>
> The views expressed, are my own and not those of my employer, or Microsoft=
,
> or anyone else associated with me, including my cats.
> -----------------------------------------------------
>
> "nick" <cipher7...@gmail.com> wrote in message
>
> news:9c2717e6-42c7-4246-aca3-56063d2dd9b8@p25g2000hsf.googlegroups.com...
> I guess I should've been more specific......
>
> I'm connecting to the network remotely from VERY far away. Basically,
> it's a home office that's on a little island about 4 hours north of
> where I live. I set everything up when I was there, but they failed to
> mention a system that was upstairs. No one will be back in until
> Wednesday.
>
> The router is on the 192.168.0.XXX network which is the network the
> upstairs system is on. The other systems use that router as a gateway
> to the Internet even though they are on the 192.168.2.XXX network. I
> was hoping I could add a route to the 0.XXX network on (that the
> upstairs computer is on) the computer I connect to from home. Then RDP
> into the upstairs machine, and change it's IP. But that isn't working
> out too well. The route command sees that the gateway is on another
> network, and won't let me add a path.

What I don't understand is how the router is connected to two
different networks yet one network can't "see" the other. If the
router is the device they have in common why can't I just connect to
the other network?

Re: Wrong Network by Phillip

Phillip
Tue Apr 08 08:41:47 PDT 2008

"nick" <cipher7836@gmail.com> wrote in message
news:31ce8451-2528-4bf8-adc6-93c583c5fdd4@a70g2000hsh.googlegroups.com...
On Apr 7, 1:39 pm, "Phillip Windell" <philwind...@hotmail.com> wrote:

> What I don't understand is how the router is connected to two
> different networks yet one network can't "see" the other. If the
> router is the device they have in common why can't I just connect to
> the other network?

It doesn't work like that.
You're on the wrong side of the router.

You have a misconfigured machine on one side of the Router, then you take
another machine on the opposite side of the router and misconfigure it the
same way the match the other machine, and want the router to "route" between
them,...there just ain't no way that's is ever going to happen.

Tomorrow is Weds when someone will be back in that office to correct the
machine for you and it will be over.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html

Troubleshooting Client Authentication on Access Rules in ISA Server 2004
http://download.microsoft.com/download/9/1/8/918ed2d3-71d0-40ed-8e6d-fd6eeb6cfa07/ts_rules.doc

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.mspx

Microsoft ISA Server Partners: Partner Hardware Solutions
http://www.microsoft.com/forefront/edgesecurity/partners/hardwarepartners.mspx
-----------------------------------------------------



Re: Wrong Network by nick

nick
Wed Apr 09 11:28:41 PDT 2008

On Apr 8, 10:41=A0am, "Phillip Windell" <philwind...@hotmail.com> wrote:
> "nick" <cipher7...@gmail.com> wrote in message
>
> news:31ce8451-2528-4bf8-adc6-93c583c5fdd4@a70g2000hsh.googlegroups.com...
> On Apr 7, 1:39 pm, "Phillip Windell" <philwind...@hotmail.com> wrote:
>
> > What I don't understand is how the router is connected to two
> > different networks yet one network can't "see" the other. If the
> > router is the device they have in common why can't I just connect to
> > the other network?
>
> It doesn't work like that.
> You're on the wrong side of the router.
>
> You have a misconfigured machine on one side of the Router, =A0then you ta=
ke
> another machine on the opposite side of the router and misconfigure it the=

> same way the match the other machine, and want the router to "route" betwe=
en
> them,...there just ain't no way that's is ever going to happen.
>
> Tomorrow is Weds when someone will be back in that office to correct the
> machine for you and it will be over.
>
> --
> Phillip Windellwww.wandtv.com
>
> The views expressed, are my own and not those of my employer, or Microsoft=
,
> or anyone else associated with me, including my cats.
> -----------------------------------------------------
> Understanding the ISA 2004 Access Rule Processinghttp://www.isaserver.org/=
articles/ISA2004_AccessRules.html
>
> Troubleshooting Client Authentication on Access Rules in ISA Server 2004ht=
tp://download.microsoft.com/download/9/1/8/918ed2d3-71d0-40ed-8e6d-...
>
> Microsoft Internet Security & Acceleration Server: Partnershttp://www.micr=
osoft.com/isaserver/partners/default.mspx
>
> Microsoft ISA Server Partners: Partner Hardware Solutionshttp://www.micros=
oft.com/forefront/edgesecurity/partners/hardwarepart...
> ----------------------------------------------------- =A0

I'd always done what you suggest. That is, I've reconfigured a machine
to be on the same network as the other guy, then done what I needed to
do, and switched it back. Such as the case when I need to mess with a
Bellsouth DSL router. I just didn't know if there was a better way to
do it. I'm a bit weak on Network+ level concepts, sad to say.

Re: Wrong Network by Phillip

Phillip
Wed Apr 09 12:43:36 PDT 2008

That's a good way to do it,...but you just have to be on the same side of
the Router when you do it. There is no way to "jump" the router.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------


"nick" <cipher7836@gmail.com> wrote in message
news:5c5fb520-8707-4643-b07a-ffbbee263896@b64g2000hsa.googlegroups.com...
I'd always done what you suggest. That is, I've reconfigured a machine
to be on the same network as the other guy, then done what I needed to
do, and switched it back. Such as the case when I need to mess with a
Bellsouth DSL router. I just didn't know if there was a better way to
do it. I'm a bit weak on Network+ level concepts, sad to say.