Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

??? about setting up a remote site

0 views
Skip to first unread message

John Motley

unread,
May 12, 1998, 3:00:00 AM5/12/98
to
Please look over the following and advise me if there are flaws in my logic or a better way to do what I am trying to do.
 
 About fifty people within my network are moving to a new office.  The new office’s network ports were split into two routing sections on the recommendation of sprint. 
 
As a result,
The Subnet for the entire remote office will be 255.252.0.0. vs. 255.255.0.0 for the main office
There will be two routers, 10.40.1.1 and 10.44.1.1.
And all IP will either be 10.40.*.* or 10.44.*.*
 
 I have tested the ports and I am able to log in to my Network across the WAN connection.  However, “log in” time is slow and I am unable to get Outlook97 to open.  It always times out.  I am going to set up a BDC today. 
 
 Questions,
  How will I know that the BDC is handling the login request???
  Do I need to edit my host or LMHost files, so Outlook will not time out???
  Is it possible to create a “Exchange” BDC ????
 
Thanks for all suggestions, insight, and instruction---
 
John Motley
Raleigh, NC  USA

Douglas Wynne Greff

unread,
May 15, 1998, 3:00:00 AM5/15/98
to
When setting up subnetting you must have a common subnet mask for your entire network.  In your case this would be 255.252.0.0  Your local subnet mask should be changed from 255 to 252.  Your bit increment is correct (4) and this would provide you with two address ranges:
 
Subnet 1     10.40.1.1    10.43.255.254
Subnet 2     10.44.1.1    10.47.255.254
 
You can create 62 subnets with a possible host population of 250K on each subnet.  (seems like a bit of overkill) 
 
  The way you currently have this configured your local hosts are not looking at the first 6 bits of the mask, but rather the entire 8 bits.  This tells the clients that all traffic is local.  Your router is probably still picking up the messages being routed across because of your default gateway specification.  Your local clients are first trying to ARP (or resolve IP to MAC) locally and when failing, tries your gateway address.  This would expain your wait or slow response.  If you have a LMHOSTS file it will also be parsed along the way.
 
I hope this info is helpful
Doug Greff, MCP
John Motley wrote in message ...
0 new messages