Re: May need to move from SBS because of connection issues
- From: "Gregg Hill" <greggmhill at please do not spam me at yahoo dot com>
- Date: Mon, 20 Oct 2008 23:44:02 -0700
Jim,
Can you connect from your own SBS server itself to a remote SBS network via
RWW instead of using a workstation going out through the SBS? That should
point out or eliminate any left over ISA-client problems
I have had your second error for a while and didn't have time to look into
it.
My setup used to be dual-NIC SBS with ISA. I removed ISA and went to a
single-NIC SBS. I have two firewalls on my LAN. One (Freedom9 freeGuard 100)
has only a handful of outbound ports allowed (8080-8099, DNS, DVR 7620-7624,
FTP, H323, HTTP, HTTPS, IMAP, NNTP, PING, POP3, RDP 3389, RDP 3390, RDP
3599, RDP 3699, 5631, SMTP, WHOIS Lookup) and is the LAN's normal gateway.
The second one (SonicWALL TZ180) still has all outbound ports allowed, and I
sometimes switch to that firewall when stuff fails to work through the
FG100. My normal gateway for the workstations (via DHCP from the SBS) is the
freeGuard 100. Ditto for the SBS itself. On the FG100, I have inbound ports
25, 443, 444, and 4125 forwarded to my SBS server.
Due to your post, I started digging. I found that if I try to go out the
FG100 firewall, log into a remote site's RWW, and then try to connect to a
computer, I get your second error (VBScript: Remote Desktop Disconnected
The client could not connect to the remote computer. Remote connections
might not be enabled or the computer might be too busy to accept new
connections. It is also possible that network problems are preventing your
connection. Please try connecting again later. If the problem continues to
occur, contact your administrator.changed my gateway to be a different ).
If I change my workstation's gateway to be the TZ180 (no outbound ports
restricted yet), then I can successfully connect to the remote computers.
That is true for remote subnets that match mine, and those that have
different subnets.
Note that my workstations go out directly through either firewall, not
through SBS. I decided to add port 4125 to my OUTBOUND allowed ports on the
FG100, and I can successfully connect to the remote sites' computers. Again,
that is true for remote subnets that match mine, and those that have
different subnets.
I recommend that you load WireShark on a workstation and monitor the packets
when you try to connect. See if traffic on port 4125 is blocked.
Thank YOU for giving me the kick in the pants to finally figure out my
problem. I hope something above helps you to find your problem.
Gregg Hill
"Jim Graue" <JimGraue@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:830F62AF-80A3-4B8F-A770-04E462B20E9C@xxxxxxxxxxxxxxxx
Hello, Susan:
My replies/comments/questions are in-line, below:
"Susan Bradley" wrote:
Jim Graue wrote:
Hello, Ms. Bradley:Susan, not Ms. :-)
My replies/comments/questions are in-line, below:
"Susan Bradley" wrote:
Jim Graue wrote:
Hello, all:I can't tell how you are connecting remotely?
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.
I'm attempting to connect to other SBS networks from my own
workstation,
which is in an SBS network. I prefer using RWW from IE browser through
well-configured firewalls, so https://differentdomain.com/remote
If VPN you probably have a IP address (192.168.16.2) that is identical
to many SBS boxes. Use the change IP address wizard to fix this.
I appreciate this approach, but I use different schema at different
locations for the reason that I would like to connect to those networks
from
my own, and, of course, the IP scheme cannot be the same at two
networks.
I RWW all the time into my home SBS, and to many other SBS boxes.
I can only RWW to my own SBS from outside, so I'm using a laptop with a
broadband wireless connection. If I attempt to do this from another
SBS, I
get the same error. This leads me to believe, now that you make your
statement regarding how easily you connect, that I am making a config
error
in more than one place.
It's not your SBS server that is blocking you here.
I'm willing to entertain any other thoughts.
Post up an ipconfig/all let's go from there.
Do you want ipconfig/all from the workstation, the SBS, or both?
SBS:
C:\Documents and Settings\Administrator>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : bernoulli
Primary Dns Suffix . . . . . . . : OCS.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : OCS.local
Ethernet adapter Network Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/100+ Management
Adapter
Physical Address. . . . . . . . . : 00-D0-B7-1A-BB-B5
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.7.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.7.1
DNS Servers . . . . . . . . . . . : 192.168.111.1
Primary WINS Server . . . . . . . : 192.168.111.1
NetBIOS over Tcpip. . . . . . . . : Disabled
Ethernet adapter Server Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com Gigabit LOM (3C940)
Physical Address. . . . . . . . . : 00-0C-6E-58-2E-CB
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.111.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.111.1
Primary WINS Server . . . . . . . : 192.168.111.1
--
Best regards,
Jim Graue
Workstation:
C:\> ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : galileo
Primary Dns Suffix . . . . . . . : OCS.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : OCS.local
OCS.local
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : OCS.local
Description . . . . . . . . . . . : 3Com EtherLink XL 10/100
PCI TX
NIC
(3C905B-TX)
Physical Address. . . . . . . . . : 00-50-04-16-97-28
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.111.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.111.1
DHCP Server . . . . . . . . . . . : 192.168.111.1
DNS Servers . . . . . . . . . . . : 192.168.111.1
Primary WINS Server . . . . . . . : 192.168.111.1
Lease Obtained. . . . . . . . . . : Saturday, October 18, 2008
1:03:31 P
M
Lease Expires . . . . . . . . . . : Sunday, October 26, 2008
1:03:31
PM
And the ip addressing is what I meant. You are not using a 192.168.16.2
so that you are different than the default.
I'm sorry; I don't mean to sound cavalier, here, but, so? It CANNOT be
that
change of default IP has anything to do with this. My choice of IP schema
is
not changing subnet, or anything else. I'm changing addresses at my
location
and the locations to which I am attempting connection because I can't have
the same address schemas at both locations. TCP/IP demands a certain
ability
to interact. It is NOT ACCEPTABLE to be unable to change simple network
settings (third octet in a non-routable scheme) and NOT be able to
communicate via RWW. Besides, I can show that this scheme works with a
workgroup-to-domain settings. There is something else underfoot. Again,
I
can connect to these networks from a broadband-wireless network, but when
I
use a MS SBS, I can't. I'm almost convinced that something in Group
Policy
is blocking desktop connections.
Vbscript error "can" be a horking up Linksys router on your side. Mess
with the MTU's or get a better router.
I appreciate the sentiment, but we're not talking cheap routers, here.
Both
sides, in all cases, are using either Multitech routers ("home" router
retails in the $250 range, the office router is about $1500), or the
default
router given by the ISP (SMC, with NAT). None of the combinations are
allowing connection to other SBS networks.
Like others have said, this isn't a SBS problem here. We get into other
SBS networks all the time.
I appreciate your experience and help, here. I believe you. I only know
that I'm unable to connect to other networks from my SBS network or from
other SBS networks.
Give me the exact error messages please?
Sure.
VBScript: Remote Desktop Disconnected. The client could not
establish a connectio to the remote computer. The most likely causes for
this error are:
1) Remote connections might not be enabled at the remote computer
2) The maximum number of connections might be exceeded at the remote
computer.
3) A network error might have occurred while establishing the connection
4) The Remote Web Workplace designated port might be blocked by a
firewall.
Or,
VBScript: Remote Desktop Disconnected
The client could not connect to the remote computer. Remote connections
might not be enabled or the computer might be too busy to accept new
connections. It is also possible that network problems are preventing
your
connection. Please try connecting again later. If the problem continues
to
occur, contact your administrator.
I get the first error message when my AV solution is installed, the second
when it is UNINSTALLED. I can strip off ISA,its SP3, and AV and get the
second message.
Also does this only occur behind your router/firewall/connection at the
office, you are sure that the issue is not replicated at another
location?
At least one other location has this problem. They are running ISA 2004
with SP3, and I cannot connect to systems in my SBS or another SBS in
either
case.
All of this applies to admin or domain user accounts, either or both
sides.
I will visit the other location and see if they are having the same issue.
Of course, no one in that network would have need to connect to another
SBS
network but me.
Thanks, again, for your attention and thoughts. I appreciate the hard
work
it takes to be helpful, and it means a lot to me to have the help of other
much more knowledgeable than myself.
--
Best regards,
Jim Graue
.
- References:
- May need to move from SBS because of connection issues
- From: Jim Graue
- Re: May need to move from SBS because of connection issues
- From: Susan Bradley
- 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
- From: Susan Bradley
- Re: 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: monitor bandwidth
- 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
|
