You probably don't need to change anything on the client. What the KB
article does is explain why it looks as you describe. That is how it should
be.
Start by checking that you can ping a LAN machine by IP from the client.
If you can, your routing is working. VPN links do not carry LAN broadcasts,
so you will need extra info to ping or map files by name. If the LAN is
running DNS and/or WINS, you should be able to use that. If not, you will
need HOSTS oe LMHOSTS files on the client with appropriate entries.
<(E-Mail Removed)> wrote in message
news:6d3401c42f33$344289f0$(E-Mail Removed)...
> I'm not following you and the KB article. What changes
> are needed on the client?
>
>
> >-----Original Message-----
> > This is not controlled by the server. See KB 254231 .
> (And it probably
> >isn't the cause of your problems!)
> >
> >"Scott" <(E-Mail Removed)> wrote in message
> >news:6d4801c42f1a$059c6fd0$(E-Mail Removed)...
> >> Help Please. I am setting up a VPN Server Session on a
> >> Windows 2003 Server and am using static addressing for
> my
> >> client. The client(Windows XP) can connect just fine
> but
> >> is not receiving the proper gateway and subnet mask
> thus
> >> he is not able to receive full access to the network.
> I
> >> cannot find any area where this addressing can be set.
> >> Thank You for your guidance.
> >
> >
> >.
> >
|