Developer Forum

Anonymous;

All the networking requirements that exist on the SBS LAN are also
requirements for remote clients.

To map a network drive, the remote client needs good NetBIOS name
resolution.

To find the ISA server, the remote client needs good NetBIOS/DNS name
resolution.

How are you passing out IP addresses to your VPN clients? Are you using
DHCP or a static pool? I recommend that you use DHCP. That way, the VPN
client machines receive IP addresses for SBS LAN Default Gateway, DNS
Server(s), WINS server(s) if these options are configured in DHCP. Once
your remote clients can resolve the IP address of the ISA server, they can
utilize it's services.

Terry McKinney
Microsoft SBS Product Support

This posting is provided "AS IS" with no warranties, and confers no rights.

I have an issue with three separate SBS2003 installations (premium, with ISA
Server) so I figure this is either by design or i'm doing something wrong..

I ran the VPN setup tool on the admin menu, and in fact a VPN client will
connect fine. Once they are connected over the internet it lets them map a
drive through dos. However, the second they connect until the second they
disconnect they lose all internet access. interestingly enough an open
Terminal services window continues fine, but they lose internet, they lose
AOL instant messanger, etc.

I have one employee who realized if he plugs his broadband right into his PC
without using a router, that he doesn't lose internet. I also tried this on
a machine that had no internet to start with (disabled lan connection and
made a dial up connection to the vpn sbs03 machine). With the dialup,
everything was good. the client conneted fine and then had internet access
through the vpn, which is what we want.

I am sure this is a simple routing or gateway issue but i don't know where
to look and don't want to spend $$$ on a microsoft support call without
hearing from the community here first

> I have an issue with three separate SBS2003 installations (premium, with
ISA
wrong..


Since these are all with ISA server...the VPN clients need to either install
the ISA Firewall client and point it to the SBS server they're VPN'd into,
or go into IE and change the proxy settings to point to the SBS server
they're VPN'd into (port 8080 is the default).

If that doesn't work, what is the specific error that comes back when they
try to do things on the Internet?

David Jones
SBS Product Team

--
This posting is provided "AS IS" with no warranties, and confers no rights.




ISA
wrong..
a
PC
on
access

I tried this and it says Cannot find find server or DNS error in IE. I tried adding the servername and port 8080, that was one of the first things i checked. I have not installed the bona fide firewall client on the pc

I just tried it again and now despite the connection it will not let me map a drive letter it is fast to say connected successfully, but the # of bytes received never increases from 396. I have better results like I mentioned in my prior email when I connect by dialing into the vpn server, at least then i can surf using the server's internet & 8080 plus I can map to drives

Is the IP range the client uses before the VPN is connected the same as the
IP range the SBS server uses? Ie, does the client use 192.168.0.XXX for an
IP address, and the SBS server also uses 192.168.0.XXX? Could you post an
ipconfig /all from the VPN client after it's connected?


David Jones
SBS Product Team

--
This posting is provided "AS IS" with no warranties, and confers no rights.




tried adding the servername and port 8080, that was one of the first things
i checked. I have not installed the bona fide firewall client on the pc.
map a drive letter it is fast to say connected successfully, but the # of
bytes received never increases from 396. I have better results like I
mentioned in my prior email when I connect by dialing into the vpn server,
at least then i can surf using the server's internet & 8080 plus I can map
to drives.

In article <OVsc$ XXXX@XXXXX.COM >, XXXX@XXXXX.COM
says...

Perhaps experts such as David might correct me if I'm wrong - but this
is by design.

If your client had internet connectivity *and* and VPN connection -
you've effectively got a connection from the internet - through to the
client, through the VPN to your server (*if* the client PC is infected
with a backdoor trojan/virus etc). Hence, I always thought that the
problem you describe is by design.

Additionally, I thought that the client VPN connectoid has properties to
allow a continued connection to the net (while VPN is connected) - and
that this is *not* recommended.

--
Duncan

> Perhaps experts such as David might correct me if I'm wrong - but this

You're 100% correct Duncan. However, once the VPN is connected, you should
still be able to connect to the Internet - just by using the SBS server
itself as the gateway, not the "actual" Internet connection the VPN client
has. Hence my initial question about the ISA firewall client and proxy
settings, since the SBS server had ISA installed, you'd need additional
configuration to access the Internet via the SBS server.

David Jones
SBS Product Team

--
This posting is provided "AS IS" with no warranties, and confers no rights.

here is the ipconfig/all. the client is succcessfully gettting 192.168.0.34 in this case assigned by the dhcp of the server 192.168.0.

Windows IP Configuratio


Host Name . . . . . . . . . . . . : tim-xhs5o3vfy7

Primary Dns Suffix . . . . . . . : SBSDOMAIN.LOCA

Node Type . . . . . . . . . . . . : Hybri

IP Routing Enabled. . . . . . . . : N

WINS Proxy Enabled. . . . . . . . : N

DNS Suffix Search List. . . . . . : SBSDOMAIN.LOCA


Ethernet adapter Wireless Network Connection 2


Connection-specific DNS Suffix . : neo.rr.co

Description . . . . . . . . . . . : Intel(R) PRO/Wireless 2200BG Network Connectio

Physical Address. . . . . . . . . : 00-0E-35-0C-20-7

Dhcp Enabled. . . . . . . . . . . : Ye

Autoconfiguration Enabled . . . . : Ye

IP Address. . . . . . . . . . . . : 192.168.0.10

Subnet Mask . . . . . . . . . . . : 255.255.255.

Default Gateway . . . . . . . . . : 192.168.0.

DHCP Server . . . . . . . . . . . : 192.168.0.

DNS Servers . . . . . . . . . . . : 24.164.100.23

24.164.100.23

Lease Obtained. . . . . . . . . . : Tuesday, May 25, 2004 2:13:17 P

Lease Expires . . . . . . . . . . : Tuesday, July 06, 2004 6:13:17 A


PPP adapter Connect to Small Business Server


Connection-specific DNS Suffix . : SBSDOMAIN.LOCA

Description . . . . . . . . . . . : WAN (PPP/SLIP) Interfac

Physical Address. . . . . . . . . : 00-53-45-00-00-0

Dhcp Enabled. . . . . . . . . . . : N

IP Address. . . . . . . . . . . . : 192.168.0.3

Subnet Mask . . . . . . . . . . . : 255.255.255.25

Default Gateway . . . . . . . . . : 192.168.0.3

DNS Servers . . . . . . . . . . . : 192.168.0.

Primary WINS Server . . . . . . . : 192.168.0.

gt; IP Address. . . . . . . . . . . . : 192.168.0.101




That would be your problem right there. The client's LAN uses 192.168.0.XXX
for addresses, and your SBS server also uses 192.168.0.XXX for addresses.
When the VPN connection connects, you have two networks that are now
connected, but that use the same IP addresses, and the VPN client has no
idea where it is supposed to send which stuff for what.

You have a couple options to make this work:

1) Make sure that all of the clients that VPN into the SBS server use a
different IP range at home, ie, change all their routers to use
192.168.1.XXX or something.

2) Change the IP address scheme of the SBS server and all internal clients
to something else, ie, 192.168.1.XXX or 192.168.16.XXX or whatever.
You can do this by running the "Change Server IP Address" tool from the
"Internet and E-mail" node of the Server Management console.

Once the VPN client's home LAN address and the SBS server's LAN address are
on different network subnets, this should work fine for you.

David Jones
SBS Product Team

--
This posting is provided "AS IS" with no warranties, and confers no rights.


"Tim Klan" < XXXX@XXXXX.COM > wrote in message
news: XXXX@XXXXX.COM ...
192.168.0.34 in this case assigned by the dhcp of the server 192.168.0.1
Network Connection
PM
AM