Problem registering SQL server over the VPN tunnel

[Sabina]

I setup the VPN client (Sonicwall) and was able sucesfully login to the office network. I succesfully registered VSS server, but I am having hard time trying to register SQL server in Enterprise Manager.
I mapped drive and connected, no problem. I can ping the server and even run a remote terminal. Just in case I added the server to both hosts and lmhosts files. However when registration wizard runs it doesn't see any of the network, only my own machine.
Port scan shows that SQL server is on port 1434.

Does anyone know what might be a problem?

Sabina

[Seryi]

I setup the VPN client (Sonicwall) and was able sucesfully login to the office network. I succesfully registered VSS server, but I am having hard time trying to register SQL server in Enterprise Manager.
I mapped drive and connected, no problem. I can ping the server and even run a remote terminal. Just in case I added the server to both hosts and lmhosts files. However when registration wizard runs it doesn't see any of the network, only my own machine.
Port scan shows that SQL server is on port 1434.

Does anyone know what might be a problem?

Sabina

А если не пользовать визард, а просто руками написать туда имя сервера?
Еще 1434 - это не стандартный порт, стандартный 1433
Так что может быть надо Client Network Utility покрутить

[Dmitry67]

1. Во первых не полагайтесь на то что SQL server правильно отброузится, это зависит от протоколов. Наберите его имя сами
2. Во вторых проверьте по какому протоколу клиент связывается с сервером
3. В третьиъ при чем тут mapped driver ? зачем ?

[Sabina]

А если не пользовать визард, а просто руками написать туда имя сервера?
Еще 1434 - это не стандартный порт, стандартный 1433
Так что может быть надо Client Network Utility покрутить

I do not think I can just change the port, there are other users....
If it is not default, can it cause a problem?

Sabina

[Sabina]

1. Во первых не полагайтесь на то что SQL server правильно отброузится, это зависит от протоколов. Наберите его имя сами

This is what I did. It did not like the servername, period. When I typed IP address, it took it, but fails on the connection. I tried IP with port number, fails on the connection too.
Also Client Network Utility has both protocols, i.e. TCP/IP too and it goes first.

2. Во вторых проверьте по какому протоколу клиент связывается с сервером

How would I do that?

3. В третьиъ при чем тут mapped driver ? зачем ?

I was just saying that it is accessible, no doubt.
Why I need drive mapping?
If I need to go look up some files on server for exmaple. Besides our application dev server on the same machine too. When I work on server side code, I am uploading server's jar there to test.

Sabina

PS. Sorry for English, no Cyr on new system yet.

[Dmitry67]

Sabina

PS. Sorry for English, no Cyr on new system yet.

Понял
Раз TCP/IP первый то по нему и связывается, только если не самом сервере не отрублен TCP/IP для SQL server.

Тогда надо пинать тех кто ставил VPN

Bonne chance !

[Sabina]

I checked Server Network Utilities setting and Named Pipes go there first. There is also custom string in properties for Named Pipes.
TCP/IP goes there second, and the port number starts with 10, so it is not 1434 at all.

As for Client Network Utility on Server, they have the same settings that I saw at my home machine: TCP/IP goes first, Named Pipe (with different string in properties) second.

The other two questions I have:
1) Do I need to have Workgroup user account in order to register the SQL server in Enterprise Manager?
2) How I can register SQL Server with EM without a wizard? Can someone point me to the webpage?

Thanks,
Sabina

[Sabina]

I resolved the problem. There was no server alias set in Client Network Utility.