Viewing companyweb page over VPN?

[David Elders]

Hi all,

Quick one here.

Just setting up an SBS box for a new customer and before we get to sticking
it onsite, I want to test [using one of our own laptops] a feature the
customer requires for certain users.

I can VPN into the box no problem - IP addressing and name resolution are
fine - we are assigned one of a static pool of addresses on the LAN IP
range. We can logon to OWA no problem across this VPN link. However, we
cannot use the http://companyweb/default.aspx url to bring up the default
company intranet site.

I realise that the standard set-up for a client computer is obviously to use
the /connectcomputer method but given that I am testing this using one of
our own laptops I'd far prefer to avoid this unless absolutely necessary.

Are we being incredibly stupid or is there something simple we're missing
here...?

Thanks in advance,

David

PS - the customer has some remote users that they basically only want to be
able to access OWA and this intranet site - at least initially... that's why
we're specifically testing this...

[Ray Fong [MSFT]]

Let's verify you do have the correct name resolution.
Once you VPN, if you "ping companyweb" and "ping companyweb.domain.local",
are you able to get back the server's internal IP?

Ray Fong
Microsoft SBS Product Support

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

[David Elders]

Hi Ray,

Thanks for the swift response! :-)

ping companyweb gets nowhere but ping companyweb.domain.local resolves
instantly

Tried browsing to 'http://companyweb.domain.local/default.aspx and got a
login box for username and password which once entered brought the page
right up.

I'm assuming something isn't 100% in the VPN name resolution to cause this
and that there is maybe something we could do to workaround it?

Regards,

David

"Ray Fong [MSFT]" <ray...@online.microsoft.com> wrote in message
news:M1ml517...@cpmsftngxa06.phx.gbl...

[David Copeland [MSFT]]

David,

So it sounds like the DNS suffix is different or possibly not specified on
the client. What OS is the client? If it's a Windows 9x client then you
may want to add the AD DNS name (for example smallbusiness.local) as the
DNS suffix. If it's a NT/2000/XP client is the machine a member of the SBS
domain? If not then if you were to manually join them to the domain, that
should put the DNS suffix with the AD DNS name, or you should be able to add
the AD DNS name to the suffix search order so that it can append
smallbusiness.local to the name companyweb to try and resolve it from DNS.

--

Hope that helps,
David Copeland
Microsoft Small Business Server Support

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

Newsgroups:
SBS v4.x : microsoft.public.backoffice.smallbiz
SBS 2000: microsoft.public.backoffice.smallbiz2000
SBS 2003: microsoft.public.windows.server.sbs

"David Elders" <david_...@hotmail.com.nospam> wrote in message
news:eqfTZK8r...@tk2msftngp13.phx.gbl...

[Ray Fong [MSFT]]

Look at the connection, it should has TCP/IP listed as one of the
properties. How about you hardcode the SBS as the WINS address and then try
to ping again.

[David Elders]

Hi Ray,

No difference. Used the suffix idea from David however and that worked a
treat.

Thanks both for the swift responses.

Cheers,

David

"Ray Fong [MSFT]" <ray...@online.microsoft.com> wrote in message

news:giCr3h8r...@cpmsftngxa06.phx.gbl...

[David Elders]

Hi David,

Worked like a dream, thank you.

Cheers for the swift response.

David

"David Copeland [MSFT]" <davi...@online.microsoft.com> wrote in message
news:#TNgKY8r...@TK2MSFTNGP14.phx.gbl...