Win 2003 server: RAS-ing from a domain at work to a workgroup at h

Hi,

I'm running a Windows 2003 server at home. My home network is not a domain,
just a workgroup. I just enabled the RAS service on my server so I could
connect to my LAN at home from work using VPN.

I can successfully connect to my home LAN from work, but for some reason the
only computer I can connect to or even ping is the RAS server itself. I have
3 other computers at home, but none of them even respond to a ping request,
even if I ping their IP address.

My home server has 192.168.2.7 and one of the other computers I've been
trying to connect to via the VPN connection has 192.168.2.6.

I connect the VPN connection and my work computer gets an IP address from my
home LAN, 192.168.2.5. I can ping the server (.7) and connect to it via
terminal services client - everything seems to work well. But the other
computer appears to be completely invisible to me. I cannot even ping it's
IP address (.6).

I've tried doing a tracert, which works fine if I trace the route to my
server (just one hop), but if I try a tracert to the other computer (.6), it
goes to 192.168.2.5 (my work PC) and then just times out after that.

I posted this question at Experts-Exchange and got help from a really
helpful expert there and we went through all kinds of settings. When I told
him that I was going from a domain at home to a workgroup at home, he told me
that he didn't really have much experience with that kind of a setup. He
also told me that he'd experienced name resolution problems, but nothing like
this, where I cannot even access the computers at home by their IP addresses.

If you've got access to EE, this is the thread I posted:
http://www.experts-exchange.com/Netw...html#a21520563

Any clues?

Sorry, this of course should've been " ... I was going from a domain at work
to a workgroup at home ...."

Ping should work, unless you specifically set up RRAS to connect only to
the server. By default you get access to the LAN machines behind the RRAS
server.

Check the LAN machines for internal firewalls which might block ping.

Even when you can access these machines you will still have problems. If
you are logged on to a domain at work, your home machines are not going to
accept your credentials for file access.

"hagur" <(E-Mail Removed)> wrote in message
news:FC58C848-3D19-4C26-A083-(E-Mail Removed)...
> Hi,
>
> I'm running a Windows 2003 server at home. My home network is not a
> domain,
> just a workgroup. I just enabled the RAS service on my server so I could
> connect to my LAN at home from work using VPN.
>
> I can successfully connect to my home LAN from work, but for some reason
> the
> only computer I can connect to or even ping is the RAS server itself. I
> have
> 3 other computers at home, but none of them even respond to a ping
> request,
> even if I ping their IP address.
>
> My home server has 192.168.2.7 and one of the other computers I've been
> trying to connect to via the VPN connection has 192.168.2.6.
>
> I connect the VPN connection and my work computer gets an IP address from
> my
> home LAN, 192.168.2.5. I can ping the server (.7) and connect to it via
> terminal services client - everything seems to work well. But the other
> computer appears to be completely invisible to me. I cannot even ping
> it's
> IP address (.6).
>
> I've tried doing a tracert, which works fine if I trace the route to my
> server (just one hop), but if I try a tracert to the other computer (.6),
> it
> goes to 192.168.2.5 (my work PC) and then just times out after that.
>
> I posted this question at Experts-Exchange and got help from a really
> helpful expert there and we went through all kinds of settings. When I
> told
> him that I was going from a domain at home to a workgroup at home, he told
> me
> that he didn't really have much experience with that kind of a setup. He
> also told me that he'd experienced name resolution problems, but nothing
> like
> this, where I cannot even access the computers at home by their IP
> addresses.
>
> If you've got access to EE, this is the thread I posted:
> http://www.experts-exchange.com/Netw...html#a21520563
>
> Any clues?

Hi,

I belive I didn't set it specifically up to connect only to the server ....
it's mostly using the default settings, if not entirely.

None of my machines at home have a firewall enabled. I don't really care
about file access, I really only need to be able to connect to them using
MSTSC, for now.

Any ideas, or is this just impossible?

"Bill Grant" wrote:

> Ping should work, unless you specifically set up RRAS to connect only to
> the server. By default you get access to the LAN machines behind the RRAS
> server.
>
> Check the LAN machines for internal firewalls which might block ping.
>
> Even when you can access these machines you will still have problems. If
> you are logged on to a domain at work, your home machines are not going to
> accept your credentials for file access.
>
> "hagur" <(E-Mail Removed)> wrote in message
> news:FC58C848-3D19-4C26-A083-(E-Mail Removed)...
> > Hi,
> >
> > I'm running a Windows 2003 server at home. My home network is not a
> > domain,
> > just a workgroup. I just enabled the RAS service on my server so I could
> > connect to my LAN at home from work using VPN.
> >
> > I can successfully connect to my home LAN from work, but for some reason
> > the
> > only computer I can connect to or even ping is the RAS server itself. I
> > have
> > 3 other computers at home, but none of them even respond to a ping
> > request,
> > even if I ping their IP address.
> >
> > My home server has 192.168.2.7 and one of the other computers I've been
> > trying to connect to via the VPN connection has 192.168.2.6.
> >
> > I connect the VPN connection and my work computer gets an IP address from
> > my
> > home LAN, 192.168.2.5. I can ping the server (.7) and connect to it via
> > terminal services client - everything seems to work well. But the other
> > computer appears to be completely invisible to me. I cannot even ping
> > it's
> > IP address (.6).
> >
> > I've tried doing a tracert, which works fine if I trace the route to my
> > server (just one hop), but if I try a tracert to the other computer (.6),
> > it
> > goes to 192.168.2.5 (my work PC) and then just times out after that.
> >
> > I posted this question at Experts-Exchange and got help from a really
> > helpful expert there and we went through all kinds of settings. When I
> > told
> > him that I was going from a domain at home to a workgroup at home, he told
> > me
> > that he didn't really have much experience with that kind of a setup. He
> > also told me that he'd experienced name resolution problems, but nothing
> > like
> > this, where I cannot even access the computers at home by their IP
> > addresses.
> >
> > If you've got access to EE, this is the thread I posted:
> > http://www.experts-exchange.com/Netw...html#a21520563
> >
> > Any clues?
>
>

"hagur" <(E-Mail Removed)> wrote in message
newsABD4339-2F95-45B2-B392-(E-Mail Removed)...
> Hi,
>
> I belive I didn't set it specifically up to connect only to the server
> ....
> it's mostly using the default settings, if not entirely.
>
> None of my machines at home have a firewall enabled. I don't really care
> about file access, I really only need to be able to connect to them using
> MSTSC, for now.
>
> Any ideas, or is this just impossible?
>
> "Bill Grant" wrote:
>
>> Ping should work, unless you specifically set up RRAS to connect only
>> to
>> the server. By default you get access to the LAN machines behind the RRAS
>> server.
>>
>> Check the LAN machines for internal firewalls which might block ping.
>>
>> Even when you can access these machines you will still have problems.
>> If
>> you are logged on to a domain at work, your home machines are not going
>> to
>> accept your credentials for file access.
>>
>> "hagur" <(E-Mail Removed)> wrote in message
>> news:FC58C848-3D19-4C26-A083-(E-Mail Removed)...
>> > Hi,
>> >
>> > I'm running a Windows 2003 server at home. My home network is not a
>> > domain,
>> > just a workgroup. I just enabled the RAS service on my server so I
>> > could
>> > connect to my LAN at home from work using VPN.
>> >
>> > I can successfully connect to my home LAN from work, but for some
>> > reason
>> > the
>> > only computer I can connect to or even ping is the RAS server itself.
>> > I
>> > have
>> > 3 other computers at home, but none of them even respond to a ping
>> > request,
>> > even if I ping their IP address.
>> >
>> > My home server has 192.168.2.7 and one of the other computers I've been
>> > trying to connect to via the VPN connection has 192.168.2.6.
>> >
>> > I connect the VPN connection and my work computer gets an IP address
>> > from
>> > my
>> > home LAN, 192.168.2.5. I can ping the server (.7) and connect to it
>> > via
>> > terminal services client - everything seems to work well. But the
>> > other
>> > computer appears to be completely invisible to me. I cannot even ping
>> > it's
>> > IP address (.6).
>> >
>> > I've tried doing a tracert, which works fine if I trace the route to my
>> > server (just one hop), but if I try a tracert to the other computer
>> > (.6),
>> > it
>> > goes to 192.168.2.5 (my work PC) and then just times out after that.
>> >
>> > I posted this question at Experts-Exchange and got help from a really
>> > helpful expert there and we went through all kinds of settings. When I
>> > told
>> > him that I was going from a domain at home to a workgroup at home, he
>> > told
>> > me
>> > that he didn't really have much experience with that kind of a setup.
>> > He
>> > also told me that he'd experienced name resolution problems, but
>> > nothing
>> > like
>> > this, where I cannot even access the computers at home by their IP
>> > addresses.
>> >
>> > If you've got access to EE, this is the thread I posted:
>> > http://www.experts-exchange.com/Netw...html#a21520563
>> >
>> > Any clues?
>>
>>
No, it is not impossible. In fact, it should work by default.

I would scrap the current RRAS config and start again. It only takes a
few miutes to do.