Showing posts with label router. Show all posts
Showing posts with label router. Show all posts

Thursday, March 22, 2012

Connection over a router!

I am using SQL 2000 and I need to connect to it through an application
that uses ADO.
- The server is on a machine that is behind a router, the router is
configured to
map port 1433 to the same port number on the machine hosting SQL server.
- And the actual network configuration shown only TCP/IP as the
communication
protocol used.
So far I did not have any luck with the connection although I am not a
network
specialist.
I was told that the router may have the DMZ configured and that may be the
reason
for connection failure.
Any ideas?
Cheers!"Enver Buzoku" <ebuzoku@.hotmail.com> wrote in message
news:uR3%23C9wwDHA.1736@.TK2MSFTNGP09.phx.gbl...
> I am using SQL 2000 and I need to connect to it through an application
> that uses ADO.
> - The server is on a machine that is behind a router, the router is
> configured to
> map port 1433 to the same port number on the machine hosting SQL server.
> - And the actual network configuration shown only TCP/IP as the
> communication
> protocol used.
> So far I did not have any luck with the connection although I am not a
> network
> specialist.
> I was told that the router may have the DMZ configured and that may be the
> reason
> for connection failure.
> Any ideas?
1) Test TCP/IP connectivity.
Use a port sniffer to determine if you can connect over TCP/IP to port 1433
on the computer.
Telnet is a poor-man's port sniffer. Open a command prompt and type
telnet 123.123.123.123 1433
Use a numeric IP address to defer name resolution issues.
If you get a blank black screen, then you have succeeded in connecting over
TCP/IP to the target machine (then just close the window, there's nothing
you can do with this connection).
If you get an error message, then you've got a problem.
2) Test SQL connectivity over TCP/IP.
Make sure you are using the TCP/IP net library to connect. Methods for this
depends a little on your environemnt and whether you have the SQL tools
installed, but you can always create a new ODBC connection from the control
panel to test this. Just be sure to specify TCP/IP in the "Client
Configuration" section.
Davidsqlsql

Thursday, March 8, 2012

connection failed when using IP address

I am trying to connect to MSDE 2000a server over the internet. I have check
and open the ports on my router pointing it to my server (1433 & 1434). But
I am still not able to connect. (Check log and port is 1433)
Does anyone know what I can try or do to resolve this problem (I have all th
e latest patches)?Hi,
Execute "srvnetcn.exe" from command prompt from the server running MSDE. In
the display scrren,
verify that tcp/ip and named pipes are enabled for the MSDE instance. If
not, enable them and then stop and
start MSDE service and try again.
Thanks
Hari
MCDBA
"dee" <anonymous@.discussions.microsoft.com> wrote in message
news:D6817B6C-6392-4BC6-9D8A-A80D9400A264@.microsoft.com...
> I am trying to connect to MSDE 2000a server over the internet. I have
check and open the ports on my router pointing it to my server (1433 &
1434). But I am still not able to connect. (Check log and port is 1433)
> Does anyone know what I can try or do to resolve this problem (I have all
the latest patches)?

connection failed when using IP address

I am trying to connect to MSDE 2000a server over the internet. I have check and open the ports on my router pointing it to my server (1433 & 1434). But I am still not able to connect. (Check log and port is 1433)
Does anyone know what I can try or do to resolve this problem (I have all the latest patches)?
Hi,
Execute "srvnetcn.exe" from command prompt from the server running MSDE. In
the display scrren,
verify that tcp/ip and named pipes are enabled for the MSDE instance. If
not, enable them and then stop and
start MSDE service and try again.
Thanks
Hari
MCDBA
"dee" <anonymous@.discussions.microsoft.com> wrote in message
news:D6817B6C-6392-4BC6-9D8A-A80D9400A264@.microsoft.com...
> I am trying to connect to MSDE 2000a server over the internet. I have
check and open the ports on my router pointing it to my server (1433 &
1434). But I am still not able to connect. (Check log and port is 1433)
> Does anyone know what I can try or do to resolve this problem (I have all
the latest patches)?

Sunday, February 12, 2012

Connecting to SQL Server over a VPN & through a router...

Hi All,
I have a NetGear combined wireless router / ADSL modem, and am
attempting to connect to SQL Server from my (wifi enabled) laptop, but
am getting a 'failed to create SSPI context' message (note that I'm
using Windows Authentication). I'm connected to my work LAN through a
SonicWall VPN. If I take the router out of the equation, I can connect
fine - even through the VPN.
Outlook also has no luck connecting - it appears that some aspect of
Windows Authentication is broken by the router being included in the
setup.
I can ping machines on my company LAN when connected through the
router, and can also connect to SQL server using the SS authentication
- so I'm not far away from being able to authenticate.
Any thoughts/help would be much appreciated.
Thanks,
Will (LemonSmasher)
Mmm... looks like I've 'solved' this. Having established the VPN
connection for the first time, I logged off of Windows, then logged
back on, reestablished the VPN connection and then authentication
worked. Must've been down to something being cached in my original
session - if anyone can shed light on this (or if its just a lucky
coincidence!), I'd be interested in hearing from you!
Will.
LemonSmas...@.hotmail.com wrote:
> Hi All,
> I have a NetGear combined wireless router / ADSL modem, and am
> attempting to connect to SQL Server from my (wifi enabled) laptop, but
> am getting a 'failed to create SSPI context' message (note that I'm
> using Windows Authentication). I'm connected to my work LAN through a
> SonicWall VPN. If I take the router out of the equation, I can connect
> fine - even through the VPN.
> Outlook also has no luck connecting - it appears that some aspect of
> Windows Authentication is broken by the router being included in the
> setup.
> I can ping machines on my company LAN when connected through the
> router, and can also connect to SQL server using the SS authentication
> - so I'm not far away from being able to authenticate.
> Any thoughts/help would be much appreciated.
> Thanks,
> Will (LemonSmasher)

Connecting to SQL Server over a VPN & through a router...

Hi All,
I have a NetGear combined wireless router / ADSL modem, and am
attempting to connect to SQL Server from my (wifi enabled) laptop, but
am getting a 'failed to create SSPI context' message (note that I'm
using Windows Authentication). I'm connected to my work LAN through a
SonicWall VPN. If I take the router out of the equation, I can connect
fine - even through the VPN.
Outlook also has no luck connecting - it appears that some aspect of
Windows Authentication is broken by the router being included in the
setup.
I can ping machines on my company LAN when connected through the
router, and can also connect to SQL server using the SS authentication
- so I'm not far away from being able to authenticate.
Any thoughts/help would be much appreciated.
Thanks,
Will (LemonSmasher)Mmm... looks like I've 'solved' this. Having established the VPN
connection for the first time, I logged off of Windows, then logged
back on, reestablished the VPN connection and then authentication
worked. Must've been down to something being cached in my original
session - if anyone can shed light on this (or if its just a lucky
coincidence!), I'd be interested in hearing from you!
Will.
LemonSmas...@.hotmail.com wrote:
> Hi All,
> I have a NetGear combined wireless router / ADSL modem, and am
> attempting to connect to SQL Server from my (wifi enabled) laptop, but
> am getting a 'failed to create SSPI context' message (note that I'm
> using Windows Authentication). I'm connected to my work LAN through a
> SonicWall VPN. If I take the router out of the equation, I can connect
> fine - even through the VPN.
> Outlook also has no luck connecting - it appears that some aspect of
> Windows Authentication is broken by the router being included in the
> setup.
> I can ping machines on my company LAN when connected through the
> router, and can also connect to SQL server using the SS authentication
> - so I'm not far away from being able to authenticate.
> Any thoughts/help would be much appreciated.
> Thanks,
> Will (LemonSmasher)