Re: Multiple Locations

From: Dave DeCoursey (mis_at_majorelectricsup.com)
Date: 10/21/04


Date: Thu, 21 Oct 2004 14:13:31 -0400

Hi Rebecca,

You asked why I joined the remote clients to the SBS domain. I guess I did
that because that's what I thought should be done. I have 4 physical
locations connected via Cisco VPN or direct lines and I wanted to be able to
easily administrator all of them. I thought that joining them all to the
domain would be the easiest way of handling this.

Because of other applicaitons, we need to keep the Cisco VPN in place,
we're using some "dumb" terminals (MS-DOS network program).

On our Windows 2k/XP machines, how can they connect to the Exchange server
and shares? If I run RRAS, can I then keep the VPN up all of the time? Will
this interfere with the Cisco VPN? Is there someplace I can go (to read) to
learn more about this option?

Thanks,
Dave DeCoursey

PS: I'm still looking into some of the other suggestions you 've given, but
the closest remote is an hour away.

"Rebecca Chen [MSFT]" <v-rebc@online.microsoft.com> wrote in message
news:e4sZBmrtEHA.768@cpmsftngxa10.phx.gbl...
> Hi Dave,
>
> Please see inline:
>
>
>
>>The client joins the domain fine, but after joining, it receives an error.
>
> The error is Semaphore timeout, correct?
>
>>As far as the Win 2k problem, I was running a non-SBS Windows 2k server,
>>and the Win 2k clients in the remote locations could not sign on, it would
>>just hang at the "Loading Personal Settings" screen until I unplugged the
>>network cable and then it would start up fine (without rebooting).
>
> In order to keep the thread clean, please open up a new thread to discuss
> this question since it is not related to the original one.
>
>>The Semaphore timeout occurs when trying to log in to the server, again
> the
>>client joins the domain just fine. I did set up a computer locally and
>>delivered it to the remote location (yesterday) and it seems to be able to
>>log in just fine, it just won't connect to the Exchange server. This would
>>make me think that when logging in, it used cached information. I can see
>>the SBS intranet (companyweb).
>
>
> I suggest you post this question to the microsoft.public.exchange.admin
> newsgroup since the Exchange guy will provide more valuable suggestions
> and
> info on all Exchange-related issue.
>
>
>>Number 5 might be where the issue is. Our local network is 47.1.1.x (102)
>>for the server, this was setup by an outside firm, I'm looking at changing
>>it to a 192.168 network. The remote sites are 192.168.3.x and 192.168.4.x.
>
> Yes, that will cause the problem. Could you let me know if there any
> particular reason for you to join the remote client to the SBS domain?
> Technically speaking, we don't recommend this. You can use VPN connection
> to visit the network share. Remote Web Workplace is a strongly function
> for
> the remote clients to logon to the SBS server, however, it is available in
> SBS 2k3.
>
> In addition, Semaphore Timeout error has indicated that this is a network
> connection problem. Please use "route add" command to set up a static
> route
> on the client side and point the route to the destination server and then
> test this issue.
>
>>For the most part, none of the remote sites are using a DHCP server, so
> all
>>of the settings are manual and I believe they are correct. The only
> question
>>comes in is the WINS server which may not be defined on all of the remote
>>clients.
>
>>The local clients connect just fine. I let the router do all of the
> firewall
>>work, I keep them turned off on the clients.
>
> I suggest you manually configure the remote client's hosts / lmhosts files
> for name resolution for SBS server and re-test this issue.
>
> If the issue persists, please gather the MPSreport on both sides and send
> it to me for research.
>
> Good luck!
>
> Best regards,
>
> Rebecca Chen
>
> MCSE2000 MCDBA CCNA
>
>
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
>
> =====================================================
>
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
>
> =====================================================



Relevant Pages

  • RE: server/connectcomputer from remote offices
    ... > Thank you for posting to the SBS Newsgroup. ... > should be SBS_LOGIN_SCRIPT.bat on the two DCs for remote clients. ... > DC not SBS 2K3 Server, unless they need to access SBS Resource (e.g. ... > the Copy button and paste the full content to the Newsgroup. ...
    (microsoft.public.windows.server.sbs)
  • RE: Remote Office Configuration Suggestions?
    ... The additional DC at the remote site, could not be the SBS server, as you ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: Can I Login to Two SBS Domains from One PC
    ... A's accounting application from 2 of company B clients. ... Run CEICW on SBS ... You have to rerun the CEICW to make sure your SBS 2003 server have right ...
    (microsoft.public.windows.server.sbs)
  • Re: Unable to Connect to Server/Client Desktop using RWW
    ... Please post the results of an ipconfig /all for the sbs server. ... I did another test after turning off the firewall on the remote. ... If port 4125 was not forwarded on the sbs machine, ...
    (microsoft.public.backoffice.smallbiz)
  • Re: Remote Desktop Problem
    ... connectivity issues in SBS Server: ... This newsgroup only focuses on SBS technical issues. ... |> this computer on the Remote tab of properties of My Computer on SBS ...
    (microsoft.public.windows.server.sbs)

Loading