Re: May need to move from SBS because of connection issues
- From: "Larry Struckmeyer [SBS-MVP]" <lstruckmeyer@xxxxxxxxxxxxxxx>
- Date: Mon, 20 Oct 2008 21:02:50 -0400
A few more questions, the answers to which will only eliminate things, probably not fix anything. :<(
After you removed ISA from the server did you remove the client from the workstation and the notebook?
Is there now, or has there ever been a third party firewall on either that could interfere with the connection?
You did say you could connect to other SBS networks, as well as your own, with the notebook if you took it to your home or to say *$'s.
You have tested the video resolution tip that SG gave you?
You haven't used a naming convention that means that your notebook or workstation would be named the same as objects on the remote networks?
When you went from, what must have been peer to peer to SBS did the router/firewall change in any way? The addition of a Watchguard and the installation of Remote Management for it would mess up the port assignments, and I suspect there are other pitfalls in other appliances as well.
All I can think of at the moment. I left you room to answer in line. <g>
Oh, one more thing, cut Super some slack. He speaks Aussie, and having just spent almost two weeks in a room with several SBS'rs from AU, they do have a different way of making their thoughts known. Not that needs or wants me to speak for him... he has done quite well here for over 10 years.
-Larry
"Jim Graue" <JimGraue@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:216081A0-9ECB-4D94-AE4C-E57495AA0485@xxxxxxxxxxxxxxxx
Hello, all:
I may need some "talking down" on the following issue: I'm unable, for
reasons unknown, to connect to other SBS networks from my own, new SBS 2K3
network. I get either a "vbscript error" message, or a more generic one,
indicating that I should contact the system admin (uh, me) if I continue to
have problems. I had ISA 2004 installed with SP3, but have since removed it.
Still, I cannot connect to another SBS network. I get as far as RWW, but
when I want to remote control a system or get a terminal session from a
terminal server, the above-mentioned errors occur.
I'm considering backing out of SBS on my own network, as I'm finding that I
need to get to other networks. I'm thinking of installing W2K3 Server and
Exchange, but I think it would mean that, by Best Practice, I shouldn't have
Exchange on a DC, right? I mean, it's only SBS, with its special
construction, that allows the mix of Exchange and DC, ISA, etc.
I've tried just about everything I can think of and a few things suggested
in posts that I've made, here, and I appreciate the help I've gotten. It's
just that I'm reaching a critical stage where not having easy access to other
SBS networks is really causing a problem. It's disappointing, because I
really liked the idea of running a network in my own business that was akin
to the type I like to install for small businesses: SBS and a Terminal
Server, along with workstations or thin clients, depending on the vertical
market package that is called for.
Probably, if I'm leaving SBS-land, I ought to be posting this in the
Exchange ng, or the general Windows 2K3 ng. But, you will politely let me
know if I've posted improperly. I beg your indulgence, in advance.
--
Best regards,
Jim Graue
.
- Follow-Ups:
- Re: May need to move from SBS because of connection issues
- From: Jim Graue
- Re: May need to move from SBS because of connection issues
- References:
- May need to move from SBS because of connection issues
- From: Jim Graue
- May need to move from SBS because of connection issues
- Prev by Date: Re: May need to move from SBS because of connection issues
- Next by Date: Re: sending spam
- Previous by thread: Re: May need to move from SBS because of connection issues
- Next by thread: Re: May need to move from SBS because of connection issues
- Index(es):
Relevant Pages
|
