Remote Desktop

Hi All,

Have the following situation.

Am able to VPN from workstation behind a SBS 2000 Server to another SBS 2000
Server. However, am unable to connect via remote desktop. The error is that
the remote computer cannot be found. Saying that I am unable to ping the
destination server either.

However I am able to successfully do this when I use a connection that is
not behind the SBS Server.

Setup is as follows

dest:
router, isa, 2 nics & static ip

The setup I am trying to connect from behind

router, isa, 2 nic & dynamic ip.

I have also tested by removing the router at the end we are trying to
connect from & still the same problem. (appears to related to the SBS at the
end we are trying to connect from)

Any idea's?

Thanks
Adam

Adam
Sat Jun 12 21:02:56 CDT 2004

I should mention that the Machine Names on both SBS's are different however
they have been figured with the same IP address scheme...

ie: internal nic: 192.168.16.x
external nic: 192.168.1.x

could this be part of the issue?



"Adam" <adam.rippon@sydneytech.com.au> wrote in message
news:uv$48hOUEHA.1952@TK2MSFTNGP12.phx.gbl...
> Hi All,
>
> Have the following situation.
>
> Am able to VPN from workstation behind a SBS 2000 Server to another SBS
2000
> Server. However, am unable to connect via remote desktop. The error is
that
> the remote computer cannot be found. Saying that I am unable to ping the
> destination server either.
>
> However I am able to successfully do this when I use a connection that is
> not behind the SBS Server.
>
> Setup is as follows
>
> dest:
> router, isa, 2 nics & static ip
>
> The setup I am trying to connect from behind
>
> router, isa, 2 nic & dynamic ip.
>
> I have also tested by removing the router at the end we are trying to
> connect from & still the same problem. (appears to related to the SBS at
the
> end we are trying to connect from)
>
> Any idea's?
>
> Thanks
> Adam
>
>
>
>
>
>
>
>
>
>
>
>

Merv
Sat Jun 12 21:39:14 CDT 2004

Yep.. most likely a problem. For proper routing to occur, the LAN networks
have to be in unique subnets. One can be 192.168.16.x; the other then has
to be in a different subnet (like 192.168.17.x).

--
Merv Porter [SBS MVP]
===================================
"Adam" <adam.rippon@sydneytech.com.au> wrote in message
news:%23m$PYrOUEHA.2560@TK2MSFTNGP10.phx.gbl...
> I should mention that the Machine Names on both SBS's are different
however
> they have been figured with the same IP address scheme...
>
> ie: internal nic: 192.168.16.x
> external nic: 192.168.1.x
>
> could this be part of the issue?
>
>
>
> "Adam" <adam.rippon@sydneytech.com.au> wrote in message
> news:uv$48hOUEHA.1952@TK2MSFTNGP12.phx.gbl...
> > Hi All,
> >
> > Have the following situation.
> >
> > Am able to VPN from workstation behind a SBS 2000 Server to another SBS
> 2000
> > Server. However, am unable to connect via remote desktop. The error is
> that
> > the remote computer cannot be found. Saying that I am unable to ping the
> > destination server either.
> >
> > However I am able to successfully do this when I use a connection that
is
> > not behind the SBS Server.
> >
> > Setup is as follows
> >
> > dest:
> > router, isa, 2 nics & static ip
> >
> > The setup I am trying to connect from behind
> >
> > router, isa, 2 nic & dynamic ip.
> >
> > I have also tested by removing the router at the end we are trying to
> > connect from & still the same problem. (appears to related to the SBS at
> the
> > end we are trying to connect from)
> >
> > Any idea's?
> >
> > Thanks
> > Adam
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
>

Duncan
Sun Jun 13 03:51:46 CDT 2004

In article <ec#xZ#OUEHA.3332@tk2msftngp13.phx.gbl>,
mwport@no_spam_hotmail.com says...
> Yep.. most likely a problem. For proper routing to occur, the LAN networks
> have to be in unique subnets. One can be 192.168.16.x; the other then has
> to be in a different subnet (like 192.168.17.x).

so what you're saying here Merv, is that is you have two default
configured SBS (say 2000, this is the 2000 NG) - then - they won't VPN
to each other due the subnetting? (thought that was the 255.255.255.0)

--
Duncan

Marina
Sun Jun 13 05:45:18 CDT 2004

Yep Duncan, that is wat Merv is saying.

--
Regards,

Marina
Microsoft SBS-MVP

"Duncan McC" <hard@work.ok> schreef in bericht
news:MPG.1b36dcc9ef18c6a989771@msnews.microsoft.com...
> In article <ec#xZ#OUEHA.3332@tk2msftngp13.phx.gbl>,
> mwport@no_spam_hotmail.com says...
> > Yep.. most likely a problem. For proper routing to occur, the LAN
networks
> > have to be in unique subnets. One can be 192.168.16.x; the other then
has
> > to be in a different subnet (like 192.168.17.x).
>
> so what you're saying here Merv, is that is you have two default
> configured SBS (say 2000, this is the 2000 NG) - then - they won't VPN
> to each other due the subnetting? (thought that was the 255.255.255.0)
>
> --
> Duncan

Kevin
Sun Jun 13 07:07:06 CDT 2004

I install customer systems with the default 192.168.16.x schema; but my home
system is installed using the 10.0.0.x schema not only to avoid the
discussed problem, but because I like to have a visible distinction with IP
addresses between my server and the customer server ... just in case.

--
Kevin Weilbacher [SBS-MVP]

"The days pass by so quickly now, the nights are seldom long"
"Duncan McC" <hard@work.ok> wrote in message
news:MPG.1b36dcc9ef18c6a989771@msnews.microsoft.com...
> In article <ec#xZ#OUEHA.3332@tk2msftngp13.phx.gbl>,
> mwport@no_spam_hotmail.com says...
> > Yep.. most likely a problem. For proper routing to occur, the LAN
networks
> > have to be in unique subnets. One can be 192.168.16.x; the other then
has
> > to be in a different subnet (like 192.168.17.x).
>
> so what you're saying here Merv, is that is you have two default
> configured SBS (say 2000, this is the 2000 NG) - then - they won't VPN
> to each other due the subnetting? (thought that was the 255.255.255.0)
>
> --
> Duncan

Adam
Sun Jun 13 08:43:20 CDT 2004

thanks all for your replies... that was it.


"Kevin Weilbacher [SBS-MVP]" <kweilbacMVP@gte.net> wrote in message
news:#5H898TUEHA.2672@TK2MSFTNGP10.phx.gbl...
> I install customer systems with the default 192.168.16.x schema; but my
home
> system is installed using the 10.0.0.x schema not only to avoid the
> discussed problem, but because I like to have a visible distinction with
IP
> addresses between my server and the customer server ... just in case.
>
> --
> Kevin Weilbacher [SBS-MVP]
>
> "The days pass by so quickly now, the nights are seldom long"
> "Duncan McC" <hard@work.ok> wrote in message
> news:MPG.1b36dcc9ef18c6a989771@msnews.microsoft.com...
> > In article <ec#xZ#OUEHA.3332@tk2msftngp13.phx.gbl>,
> > mwport@no_spam_hotmail.com says...
> > > Yep.. most likely a problem. For proper routing to occur, the LAN
> networks
> > > have to be in unique subnets. One can be 192.168.16.x; the other then
> has
> > > to be in a different subnet (like 192.168.17.x).
> >
> > so what you're saying here Merv, is that is you have two default
> > configured SBS (say 2000, this is the 2000 NG) - then - they won't VPN
> > to each other due the subnetting? (thought that was the 255.255.255.0)
> >
> > --
> > Duncan
>
>

Adam
Sun Jun 13 16:39:13 CDT 2004

sorry guys... but now seem to have the issue that i cannot get connect using
rdp unless I disable the local firewall client. (if i do this is I am able
to login straight away)...

any ideas ?

fyi: i have checked
"Adam" <adam.rippon@sydneytech.com.au> wrote in message
news:eYjuvyUUEHA.2028@TK2MSFTNGP11.phx.gbl...
> thanks all for your replies... that was it.
>
>
> "Kevin Weilbacher [SBS-MVP]" <kweilbacMVP@gte.net> wrote in message
> news:#5H898TUEHA.2672@TK2MSFTNGP10.phx.gbl...
> > I install customer systems with the default 192.168.16.x schema; but my
> home
> > system is installed using the 10.0.0.x schema not only to avoid the
> > discussed problem, but because I like to have a visible distinction with
> IP
> > addresses between my server and the customer server ... just in case.
> >
> > --
> > Kevin Weilbacher [SBS-MVP]
> >
> > "The days pass by so quickly now, the nights are seldom long"
> > "Duncan McC" <hard@work.ok> wrote in message
> > news:MPG.1b36dcc9ef18c6a989771@msnews.microsoft.com...
> > > In article <ec#xZ#OUEHA.3332@tk2msftngp13.phx.gbl>,
> > > mwport@no_spam_hotmail.com says...
> > > > Yep.. most likely a problem. For proper routing to occur, the LAN
> > networks
> > > > have to be in unique subnets. One can be 192.168.16.x; the other
then
> > has
> > > > to be in a different subnet (like 192.168.17.x).
> > >
> > > so what you're saying here Merv, is that is you have two default
> > > configured SBS (say 2000, this is the 2000 NG) - then - they won't VPN
> > > to each other due the subnetting? (thought that was the 255.255.255.0)
> > >
> > > --
> > > Duncan
> >
> >
>
>

Duncan
Sun Jun 13 20:11:11 CDT 2004

In article <#5H898TUEHA.2672@TK2MSFTNGP10.phx.gbl>, kweilbacMVP@gte.net
says...
> I install customer systems with the default 192.168.16.x schema; but my home
> system is installed using the 10.0.0.x schema not only to avoid the
> discussed problem, but because I like to have a visible distinction with IP
> addresses between my server and the customer server ... just in case.

Cheers all for the clarification - what method could one use for
changing the (server) IP address to say a 10.10 in SBS 2000 (saw
somewhere here that there is a "change IP wizard" for 2003 - how's about
2000) ???

--
Duncan

Duncan
Sun Jun 13 20:13:11 CDT 2004

In article <O5epq8YUEHA.2944@tk2msftngp13.phx.gbl>,
adam.rippon@sydneytech.com.au says...
> sorry guys... but now seem to have the issue that i cannot get connect using
> rdp unless I disable the local firewall client. (if i do this is I am able
> to login straight away)...

I don't have XP here, but presumably it can be configured in the
Advanced tab of your ICF.

--
Duncan

Marina
Mon Jun 14 05:18:10 CDT 2004

No Wizard in SBS 2000. Change the IP on the internal nic, then change
DHCP-server, WINS and DNS. Rerun ICW wizard.

--
Regards,

Marina
Microsoft SBS-MVP

"Duncan McC" <hard@work.ok> schreef in bericht
news:MPG.1b37c25eb1d9ba13989772@msnews.microsoft.com...
> In article <#5H898TUEHA.2672@TK2MSFTNGP10.phx.gbl>, kweilbacMVP@gte.net
> says...
> > I install customer systems with the default 192.168.16.x schema; but my
home
> > system is installed using the 10.0.0.x schema not only to avoid the
> > discussed problem, but because I like to have a visible distinction with
IP
> > addresses between my server and the customer server ... just in case.
>
> Cheers all for the clarification - what method could one use for
> changing the (server) IP address to say a 10.10 in SBS 2000 (saw
> somewhere here that there is a "change IP wizard" for 2003 - how's about
> 2000) ???
>
> --
> Duncan