August 20, 2004 at 1:12 pm
What started out as a minor inconvenience is becoming a real problem. I'm hoping someone can give a me a clue to solving it.
We have 30-40 SQL Servers. One of them, our development server of course, stopped showing up in the list of Available Servers one day. This is the list that you get if you try to register a new server and click the ... button. Now, I know that happens sometimes and I typed in the name directly and it registered successfully. I found it a little odd because it had been in the list before and suddenly wasn't. But, I was able to continue on my way.
Then, I tried to access that same server from home in the same way I access our other servers from home. It was, of course, not in my list, but typing in its name didn't work this time. I have accessed the others sucessfully from home. Frustrated, I had to come into work that day.
Now, I'm trying to test out Crystal Reports 10 and hook up to that same server to view OLAP cubes. There is no list to pick from here, and when I type the name in and test the connection, it is successful. However, when I try to browse that server to pick a cube, it fails.
I believe these conditions are all related, but I've got no idea why or where to look for the answer. Can anyone point me in the right direction?
Thanks,
Jana
August 20, 2004 at 2:13 pm
I would suggest that you (or your network people) take a look at the TCP/IP settings, especially subnet masks, along with the DNS/DHCP, and if any routers/switches/hubs are blocking it IP address.
Just my $0.02
----------------
Jim P.
A little bit of this and a little byte of that can cause bloatware.
August 20, 2004 at 8:44 pm
I'll expand a bit on what Jim said.
The way a SQL Server "advertises" its presence is with the SQL Server listener service. That's how you see it in your drop down list. If, for whatever reason, your request can't get to the SQL Server or the SQL Server can't respond, you won't see it in any of the lists. Jim is right in getting with your network people about this... your request is udp/1434 broadcast (sent to 255.255.255.255), if that helps them.
As far as locating the server from home, what you may try next time is drop down to the command prompt and attempt to ping it. If you get unknown host, you're not able to resolve the server name to an IP address, hence the reason you can't get there. As Jim indicates, this may be a DNS issue. You didn't say how you're connecting into work... VPN, Citrix, etc., so it's hard to give you exact guidance, but again, your network folks can help you determine why the server name isn't resolving, if that's the case.
If you just can't get to the server but you can resolve the name (for instance, your ping down show the name and IP address but you get timeouts for the 4 pings), it may be for whatever reason access to that development server is blocked. In our environment we've done that in certain cases.
K. Brian Kelley
@kbriankelley
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply