Wrong Network

[nick]

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?

 

[Phillip Windell]

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]

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 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.
-----------------------------------------------------






- 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.

 

[goarilla]

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)

 

[Phillip Windell]

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.
-----------------------------------------------------

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.

 

[nick]

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.
-----------------------------------------------------


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?

 

[Phillip Windell]

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
-----------------------------------------------------

 

[nick]

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 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 2004http://download.microsoft.com/download/9/1/8/918ed2d3-71d0-40ed-8e6d-...

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

Microsoft ISA Server Partners: Partner Hardware Solutionshttp://www.microsoft.com/forefront/edgesecurity/partners/hardwarepart...
-----------------------------------------------------  

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.

 

[Phillip Windell]

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.
-----------------------------------------------------


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.