Bridge a dialup connection to a subnet

[Bob B]

I have a static public subnet on which I have 10 or so
workstations/controllers. Some of the instruments I need to control are on
the net. I have a Novell file server with all my user software on it. I
have one test facility that is a mile or so away with only AC power and a
phone line. I have setup an old pc with ras to accept dial-in connections
and to route the tcp/ip on to the instrumentation. This has worked well
with win95 controllers for several years. I upgraded to XP. Now I can dial
in to my remote station but to see the remote instruments I have to disable
the lan connection. Now I can't get to my programs that are on my server!
If I leave the lan connection active, I can ping both side on the ras router
but nothing beyond.

How do I fix this? Can I tweek the route table. What about "bridging"? It
seems bridging to a dialup is not allowed. Any ideas?

Thanks
Bob B

[Daniel Carwile]

Could it be the built in firewall in XP?

"Bob B" > wrote in message
...
> I have a static public subnet on which I have 10 or so
> workstations/controllers. Some of the instruments I need to control are
on
> the net. I have a Novell file server with all my user software on it. I
> have one test facility that is a mile or so away with only AC power and a
> phone line. I have setup an old pc with ras to accept dial-in connections
> and to route the tcp/ip on to the instrumentation. This has worked well
> with win95 controllers for several years. I upgraded to XP. Now I can
dial
> in to my remote station but to see the remote instruments I have to
disable
> the lan connection. Now I can't get to my programs that are on my server!
> If I leave the lan connection active, I can ping both side on the ras
router
> but nothing beyond.
>
> How do I fix this? Can I tweek the route table. What about "bridging"?
It
> seems bridging to a dialup is not allowed. Any ideas?
>
> Thanks
> Bob B
>
>

[Bob B]

No. The firewall is turned off. The blocked access to the Novell server
has to do with the way Microsoft implements IPX it think.

Bob
"Daniel Carwile" > wrote in message
...
> Could it be the built in firewall in XP?
>
> "Bob B" > wrote in message
> ...
> > I have a static public subnet on which I have 10 or so
> > workstations/controllers. Some of the instruments I need to control are
> on
> > the net. I have a Novell file server with all my user software on it.
I
> > have one test facility that is a mile or so away with only AC power and
a
> > phone line. I have setup an old pc with ras to accept dial-in
connections
> > and to route the tcp/ip on to the instrumentation. This has worked well
> > with win95 controllers for several years. I upgraded to XP. Now I can
> dial
> > in to my remote station but to see the remote instruments I have to
> disable
> > the lan connection. Now I can't get to my programs that are on my
server!
> > If I leave the lan connection active, I can ping both side on the ras
> router
> > but nothing beyond.
> >
> > How do I fix this? Can I tweek the route table. What about "bridging"?
> It
> > seems bridging to a dialup is not allowed. Any ideas?
> >
> > Thanks
> > Bob B
> >
> >
>
>