We've scoured through all the related kb articles we could find and
even attempted to read every vpn related post here, and some of the
resolutions we found here helped us, but we're still missing
something. We're so confused as to why the router is still preventing
a connection. Ironically, from the office location, the local
computers there can at least establish a partial connection with the
server, but then return an error message on the Verifying
Username/Password step. I'm not sure why I would fail to connect at
all, and they can only partially connect.
If we can connect to the server's vpn internally with the 192.168.x.x
address and it works, does that 100% mean it's the router that's
causing the problem?
Any ideas would be gladly appreciated, we are getting desperate!
David
What you need to do is open up multiple ports 1723 + secondary ports on the
inbound direction and forward them to the SBS server. Another option is to put
the SBS server into the DMZ and have all traffic destined for the SBS Server
automatically sent to the SBS machine (less secure, easier to set up)
--
Mike Chan
Technical Product Manager (ISA Server/VPN)
Security Business Unit
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
--
"David" <kswi...@yahoo.com> wrote in message
news:1e78b74e.03022...@posting.google.com...
Good news is we got it working today, we're able to connect and get
authenticated.. bad news is that once connected, we still dont see the
office workgroup in my network places. The sbs server works off a
domain, but even when we log on via vpn with user/pass AND domain,
still nothing except the local workgroup, nothing server oriented.
What could we be missing now?
David
"Mike Chan [MSFT]" <mc...@online.microsoft.com> wrote in message news:<Ow32JlU3...@TK2MSFTNGP12.phx.gbl>...
Can you access the resouces through the IP?
The main reason why things like this don't work are that workgroup info is
usually due to broadcast information, but broadcast packets usually do not pass
through VPN tunnels. If you do not have a domain infrastructure to get that
information out, I'm not sure exactly how to fix this. Maybe someone has
suggestions on how to get this to work automatically =)
--
Mike Chan
Technical Product Manager (ISA Server/VPN)
Security Business Unit
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
--
"David" <kswi...@yahoo.com> wrote in message
news:1e78b74e.03022...@posting.google.com...
I'm getting this notice when I connect, does this have anything to do
with it:
One or more requested network protocls did not connect successfully.
TCP/IP CP connected successfully.
IPX/SPX or compatible CP reported error 733: A connection to the
remote computer could not be completed. You might need to adjust the
protocols on this computer...
I didn't even have IPX/SPX installed on my machine, so I installed it
thinking maybe it was missing it.. same error.. but i can just discard
the error and allow the connection -- so it works.. just kind of.. is
this a problem I need to fix? or should I check the box that says "Do
not request the failed protocls next time"?
Thanks for your help, David
"Mike Chan [MSFT]" <mc...@online.microsoft.com> wrote in message news:<OuIgs9W3...@TK2MSFTNGP11.phx.gbl>...
You don't need IPX/SPX.
Have you tried accessing the fileshares by IP? You may want to make your servers
static and set up local hostnames.
--
Mike Chan
Technical Product Manager (ISA Server/VPN)
Security Business Unit
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
--
"David" <kswi...@yahoo.com> wrote in message
news:1e78b74e.03022...@posting.google.com...
--
Nir [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
--
"David" <kswi...@yahoo.com> wrote in message
news:1e78b74e.03022...@posting.google.com...