Hi

I have just reinstalled my sbs2000 using the ip 10.0.0.2/255.255.255.0. I am
now trying to vpn to a remote sbs 2000 with ip 192.168.16.2/255.255.255.0.
The problem is that when I am connected, I get an address in the range
192.168.16.x from the remote dhcp but the subnet mask is 255.255.255.255!!!
I then have problem in logging in to the terminal services on the remote
sbs2000. Are these two connected? What can I do to fix this?

Thanks

Regards

Re: vpn ip issuing problem by David

David
Mon Jun 14 13:14:35 CDT 2004

Yes, this is normal to get a 255.255.255.255 subnet mask from the VPN
connection.
Once you connect, can you ping the IP address or name of the SBS 2000
machine? Can you access things other than Terminal Services on the remote
network?

David Jones
SBS Product Team

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


"John" <john@nospam.infovis.co.uk> wrote in message
news:%23M7CPpfUEHA.2944@tk2msftngp13.phx.gbl...
> Hi
>
> I have just reinstalled my sbs2000 using the ip 10.0.0.2/255.255.255.0. I
am
> now trying to vpn to a remote sbs 2000 with ip 192.168.16.2/255.255.255.0.
> The problem is that when I am connected, I get an address in the range
> 192.168.16.x from the remote dhcp but the subnet mask is
255.255.255.255!!!
> I then have problem in logging in to the terminal services on the remote
> sbs2000. Are these two connected? What can I do to fix this?
>
> Thanks
>
> Regards
>
>



Re: vpn ip issuing problem by Robert

Robert
Mon Jun 14 13:34:47 CDT 2004

John,

The 255.255.255.255 subnet mask is normal. Here are my IP settings when
connected to a working VPN.

IP Address: 192.168.16.61
Subnet Mask: 255.255.255.255
Default Gateway: 192.168.16.61
DNS Servers: 192.168.16.2
192.168.16.2
Primary WINS Server: 192.168.16.2
Secondary WINS Server: 192.168.16.2

You can probably ping machines on the remote network. I think you have some
other problem. Maybe a firewall issue.

Robert Harris

"John" <john@nospam.infovis.co.uk> wrote in message
news:%23M7CPpfUEHA.2944@tk2msftngp13.phx.gbl...
> Hi
>
> I have just reinstalled my sbs2000 using the ip 10.0.0.2/255.255.255.0. I
am
> now trying to vpn to a remote sbs 2000 with ip 192.168.16.2/255.255.255.0.
> The problem is that when I am connected, I get an address in the range
> 192.168.16.x from the remote dhcp but the subnet mask is
255.255.255.255!!!
> I then have problem in logging in to the terminal services on the remote
> sbs2000. Are these two connected? What can I do to fix this?
>
> Thanks
>
> Regards
>
>



Re: vpn ip issuing problem by John

John
Mon Jun 14 16:08:03 CDT 2004

I can ping various machines including server by can't do much else. Trying
to accessing server file system by typing \\192.168.16.2\ in windows
explorer gives 'Windows can not find 192.168.16.2'. ts client says the
server may be too busy.

Regards

"David Jones [MSFT]" <dajones@online.microsoft.com> wrote in message
news:ueDbotjUEHA.704@TK2MSFTNGP09.phx.gbl...
> Yes, this is normal to get a 255.255.255.255 subnet mask from the VPN
> connection.
> Once you connect, can you ping the IP address or name of the SBS 2000
> machine? Can you access things other than Terminal Services on the remote
> network?
>
> David Jones
> SBS Product Team
>
> --
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
>
> "John" <john@nospam.infovis.co.uk> wrote in message
> news:%23M7CPpfUEHA.2944@tk2msftngp13.phx.gbl...
> > Hi
> >
> > I have just reinstalled my sbs2000 using the ip 10.0.0.2/255.255.255.0.
I
> am
> > now trying to vpn to a remote sbs 2000 with ip
192.168.16.2/255.255.255.0.
> > The problem is that when I am connected, I get an address in the range
> > 192.168.16.x from the remote dhcp but the subnet mask is
> 255.255.255.255!!!
> > I then have problem in logging in to the terminal services on the remote
> > sbs2000. Are these two connected? What can I do to fix this?
> >
> > Thanks
> >
> > Regards
> >
> >
>
>



Re: vpn ip issuing problem by John

John
Mon Jun 14 16:09:19 CDT 2004

I can ping various machines including serverelse. ts client says the server
may be too busy.

Regards

"Robert Harris" <robertharris@robertharris!com> wrote in message
news:%23zoGE5jUEHA.3420@TK2MSFTNGP12.phx.gbl...
> John,
>
> The 255.255.255.255 subnet mask is normal. Here are my IP settings when
> connected to a working VPN.
>
> IP Address: 192.168.16.61
> Subnet Mask: 255.255.255.255
> Default Gateway: 192.168.16.61
> DNS Servers: 192.168.16.2
> 192.168.16.2
> Primary WINS Server: 192.168.16.2
> Secondary WINS Server: 192.168.16.2
>
> You can probably ping machines on the remote network. I think you have
some
> other problem. Maybe a firewall issue.
>
> Robert Harris
>
> "John" <john@nospam.infovis.co.uk> wrote in message
> news:%23M7CPpfUEHA.2944@tk2msftngp13.phx.gbl...
> > Hi
> >
> > I have just reinstalled my sbs2000 using the ip 10.0.0.2/255.255.255.0.
I
> am
> > now trying to vpn to a remote sbs 2000 with ip
192.168.16.2/255.255.255.0.
> > The problem is that when I am connected, I get an address in the range
> > 192.168.16.x from the remote dhcp but the subnet mask is
> 255.255.255.255!!!
> > I then have problem in logging in to the terminal services on the remote
> > sbs2000. Are these two connected? What can I do to fix this?
> >
> > Thanks
> >
> > Regards
> >
> >
>
>