Re: SQL Server 2005 Connection Problems



Hi Steve,

I have a similar problem here. I can't see instances of SQLEXPRESS on othe
machines in my domain (it's a small LAN connected to an SBS2003 box) no
matter what I do. The points are these:
a. no matter what the cause is, I don't think I'm in an unusual situation:
I'm an experienced IT guy, no doubt with many gaps in my knowledge, who just
can't get this product to work in a relatively simple environment. Since I
couldn't do it 6 months or so ago during the beta either (and said so), my
inclination is to believe that
- I am not alone
- Microsoft people have discounted the difficulties of users such as
myself because you aren't seeing enough problem reports. But many people
will give up before they post problem reports and will simply not use the
product.
b. SQL Server Express is such a powerful tool that it would be a shame if
takeup is limited because people simply cannot get it to work
c. the documentation about IP addresses goes so far, but it doesn't really
pin down what's going on beyond a certain point. Just by way of example,
- nothing I've seen explains what Microsoft understands by a "Dynamic IP
address" (and of course, you have to bear in mind that there is probably
another interpretation of "Dynamic IP")
- it is't completely clear what the SQL Server Browser is for. OK, it might
be clear to people who have the full SQL Server and understand what it's
there for, but people who are trying to follow what they perceive to be an
MS lead may not have that expertise.
d. What would really be helpful would be some really simple diagnostic
tools that would enable users to see, as far as possible, exactly why a
connection reqest was being rejected. it only takes a few moments' thought
to realise that the easier MS makes it to diagnose connectivity problems,
the less likely users are to employ drastic solutions (such as switching off
their firewalls) to solving such problems.

Best regards,

Peter Jamieson

(Former Word MVP)

"Steven Cheng[MSFT]" <stcheng@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:GQPKrbIMGHA.668@xxxxxxxxxxxxxxxxxxxxxxxx
Thanks for your response Trex,

I think the problem is still likely the the port is blocked by some
firewall between the server and that client. As you mentioned another
client in the same intranet can visit that port, so there may have some
other firewall between the two intranet which block this port. Have you
tried using telnet to ping that SQL 2K5's listening port from
commandline(on the problem client mac hine) to see whether it works?

Regards,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)



.



Relevant Pages

  • Re: interfaces lo:1 lo:2 lo:3? (for remote ssh tunnels)
    ... That's the problem tunneling (port forwarding) solves. ... >>can't get past the client firewall. ... > I don't understand why the server would be making the ... server initiates another connection to the client -- in this ...
    (Debian-User)
  • Re: Using Remote Desktop From an SBS Domain
    ... when you tried to RDP while attached directly to a port on your router? ... So if 3389 needs forwarded on the client end too then that is what the ... Hopefully next week I can attempt a connection while my ISP watches the ...
    (microsoft.public.windows.server.sbs)
  • RE: Telnet/ftp problems SBS2000
    ... Please make sure your client computers are configured as both Firewall ... will find two options "Enable folder view for FTP sites" and "Use Passive ... that the control connection has been successfully established, ... (other than port 21) ...
    (microsoft.public.windows.server.sbs)
  • Re: One workstation cant access email from ISP - CROSSPOST
    ... Remove or disable the ISA Firewall client. ... Ethernet adapter Wireless Network Connection: ... Switch is nothing more than a patch panel; ... port - same result. ...
    (microsoft.public.exchange.admin)
  • Re: Processs PreciseMail AntiSpam Gateway - any experience so far ?
    ... >> another machine or port on the user's home network. ... >> connection to an external machine having been made or by the user explicitly ... > use a well-known port that the NAT firewall forwards to the client ...
    (comp.os.vms)