Re: Access to SQL Server 2000 remotely

You can also try by Start -> Run -> cmd
and then write the comand
telnet <server_name> <port_number>
this will run telnet. If screen goes black and cursor will show you have acces to the serwer.

--
Mariusz Koprowski

"Jose Perdigao" <JosePerdigao@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:95A1ADE8-C3EE-4878-A81C-3A8AE2075E64@xxxxxxxxxxxxxxxx
Where Can I find microsoft telnet tool? I tried to find microsoft downloads
but I didn't find.

Could you help me?

Thanks

"Manikanth" wrote:

You can use a microsoft telnet tool to find out whether you can telnet into
the destination server on a particular port. On the destination server side,
do a netstats to find out the list of portnumbers that are already being
used.

By default, 1433 is the port no that sql server listens on. You can change
it using server network utility. However
when the client tries to connect, make sure that the client network uility
is also configured with the port number changes.

thks,
Mani


"Jose Perdigao" <JosePerdigao@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2980F9B4-FA99-4D1F-925A-42C95F039AE4@xxxxxxxxxxxxxxxx
> How can i see the ports available?
>
> Thanks
>
> "Kevin3NF" wrote:
>
>> IT probably has the port blocked on the firewall, as they should. Let
>> them
>> know the port your SQL Server is using (viewable in the SQL Server
>> Errorlog
>> if you are not sure)
>>
>> -- >> Kevin Hill
>> 3NF Consulting
>> http://www.3nf-inc.com/NewsGroups.htm
>>
>> Real-world stuff I run across with SQL Server:
>> http://kevin3nf.blogspot.com
>>
>>
>> "José" <Jos@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:2830F020-B38D-45A1-A490-5BF48A26269A@xxxxxxxxxxxxxxxx
>> >I have installed SQL Server at my home computer. I can access from
>> >another
>> > computer over internet. But from my company, I can't.
>> >
>> > I talk to IT administrator, but he doesn't understand a lot abou >> > this
>> > issue.
>> > Any help?
>> >
>> > What th IT should do to I have access?
>> >
>> > Thanks,
>> > Jose
>> >
>>
>>
>>



.

Relevant Pages

  • Re: ADP problems after SQL 2005 Upgrade
    ... Use the SQL Server Configuration Manager to create aliases; ... each port can be associated only with a single instance. ... Sylvain Lafontaine, ing. ...
    (microsoft.public.access.adp.sqlserver)
  • [NT] Microsoft SQL Server 2000 Unauthenticated System Compromise
    ... The following security advisory is sent to the securiteam mailing list, and can be found at the SecuriTeam web site: http://www.securiteam.com ... Microsoft's database server SQL Server 2000 exhibits two buffer-overrun ... clients connecting to TCP port 1433 or both. ... This message is a single byte packet, ...
    (Securiteam)
  • Re: Do SqlServer 2000 & SqlServer 2005 co-exist
    ... Either SQL Server 2000 or SQL Server 2005. ... So you have to move one of them to another port. ... You could allow an program exception in your firewall instead of a port number exception. ... I understand that you can connect to SQL 2000 named instance on the local ...
    (microsoft.public.sqlserver.setup)
  • Re: IIS, SQL 2000 & XPs Firewall
    ... Only one instance of SQL Server can use TCP port 1434. ... You may find it easier to use SQL Server Configuration Manager ... 2008 will be a named instance ... you will have to open those as exceptions in the firewall. ...
    (microsoft.public.sqlserver.connect)
  • Re: Is there any way to prevent hacker trying to guess sa password?
    ... and port 1433 will not be open. ... If someone can crash SQL Server by connecting to port 1433, ... You don't need multiple security experts. ...
    (microsoft.public.sqlserver.security)