Re: Specified network name is no longer available
- From: jdr.smith@xxxxxxxxxx
- Date: Sun, 2 Dec 2007 01:43:57 -0800 (PST)
Perhaps your site C link has developed some packet loss, latency problems or
something along those lines. Perhaps a call to the provider and looking at
lower level counters for the circuit/link would be in order.
ISP says nothing wrong with the connection..
Also it works just fine if the guys make a dial up VPN connection to
either Site A or Site B..wierd.
Mind you I've seen a few posts here regarding putting SBS2003 onto a
multiple site setup and it not being the best on things to do,
especially with ISA 2004 on the SBS2003 and also multihomed.
So I'm kind of off into the realm of the unknown perhaps ?
What we've got are two main sites and two branch sites, well sort of..
The main site, Site A had SBS 2003 Premium before all the other sites
came into exsitence, ie the company grew rapidly.
On it's own the SBS2003 server worked well, SBS is great isn't it.
We've had SBS from the outset starting with SBS 4.0 then SBS 4.5
followed by SBS2000 and then the current SBS2003.
Anyway there was a need to move all the sales guys to another site.
So Site B was setup.
As we could only afford a 2Mbps datastream ( and that was expensive
enough )we decided that we really needed a server at site B to cope
with the users data etc et.
So Site B had a Windows Server 2003 setup as an additional DC on the
same domain with DNS/DHCP/GC (no WINS, might have been a mistake ?)
Site B also has it's own internet connection seperate to the intersite
datastream link.
This internet connection is multihomed on the Windows Server 2003.
So both sites have in effect multihomed connections to the internet
seperate to the intersite hardware routed VPN between them.
Only one Exchage 2003 Server at Site A.
All users at Site B access Exchange across the intersite link.
Though they logon and access their data locally at Site B.
The sites/subnets are setup in Active Directory Sites & Services and
are also setup in ISA 2004 as Internal and also setup in Connection
Limits as well.
Both sites replicate across the intersite link OK and thus far it was
working very well.
It was then decided to have two more remote sites, one in the UK and
another in the US.
These sites were not going to have servers.
So we setup Site C in the UK used the same hardware VPN router and
connected Site C to both Sites A and Site B so that users at Site C
could access data from servers at Site A and Site B and get their mail
from Exchange at Site A.
Sites C only has single broadband connection for internet which it
shares with it's VPN tunnels to Sites A and B.
Site C has a small number of laptop users, max of five when they are
all in the office.
Then we did exactly the same for Site D in the US.
Site D has a couple of static PC's
We also added these sites in ISA 2004 etc and I think that I was
advised at some point to assign Site C and Site D subnets onto Site A
in Active Directory Sites & Services.
I'm not sure that this was the right thing to do ?
Anyway all was working well still..probably for about a year.
We had the odd funny with the guys from Site C as they often up sticks
and visit the LAN at Site A and/or Site B.
As you can imagine this caused a bit of a flurry with DNS.
Anyway, as of a couple of weeks ago things have gotten weird at Site
C.
The guys there to start off with were having Exchange conenctivity
problems and could not access shares at Site A.
The appeared to only be able to access things at Site B.
They then discovered that if they made a dial up VPN to Site A then
everything worked OK.
This went on for a short while, and then following some server
restarts for Windows Updates we found that the problem swapped
around..they could now only access things at Site A and no longer at
Site B.
If they attempted to open a share at Site B after a long pause they
would get 'Specified Network name is no longer available' etc as per
original post.
Same thing again, if they make a dial up VPN to Site B then everything
works OK.
Like I said earlier I can open up some folders, ie ones with nothing
in them, but any folder with lots of data just refuses to open.
I've not travelled there yet as they are some distance away, so I've
been looking at this from afar just now.
I'm probably going to go there either with a new VPN router or factory
reset theirs.
I've already rebuilt all the tunnels yesterday, didn't make a jot of
difference.
Needless to say Site D doesn't have any of these problems and has
virtually the same setup, other than Sites A, B and C are all with the
same UK ISP, the US site is with a stateside ISP.
Currently I've shipped a test laptop to Site C and am trying this out,
with the same results as the guys laptops.
I'm just trying to disjoin from the domain and re-join..that's proving
to be fun.
As I've mentioned before everything pings and resolves OK and
everthing seems to appear in DNS OK at Site A and Site B it being AD
intergrated DNS.
I've a feeling this is down to something to do with the guys at Site C
moving around LAN's, but am puzzled as to why it worked for so long in
the first place.
But I'm also getting Browser issues/events in the events logs.
I don't appear to have any server set to IsDomainMaster anywhere.
Could this be an issue ?
Anyway, thanks for your time/help thus far.
Jim.
.
- Follow-Ups:
- Re: Specified network name is no longer available
- From: jdr . smith
- Re: Specified network name is no longer available
- Prev by Date: Re: NAT for Outlook via the Internet
- Next by Date: Problem in sending emails
- Previous by thread: Installing multiple SBS VPN clients
- Next by thread: Re: Specified network name is no longer available
- Index(es):
Relevant Pages
|
