Link to home
Start Free TrialLog in
Avatar of hiteshas
hiteshas

asked on

Unable to Access MSDE from Windows 2003 over dialup.

Hi,
I have setup MSDE on a Windows 98SE system and SQL Server 2000 on a Windows 2003 Server. I have enabled NETBIOS over TCPIP on the Windows 2003 server system. I have a dial up connection established between the two systems. I am able to ping between both the computers successfully using both, the computer names as well as their IPs. Using Enterprize Manager, I am able to register the Windows 2003 SQL Server on the Windows 98 system.

But I am not able to register the Windows 98 MSDE instance in Enterprize Manager on the Windows 2003 system. I keep getting the message that the specified SQL Server does not exist or access denied.

I have added the entry into the HOSTS file, I have tried making the alias for the MSDE system using the Client Network utility. But nothing seems to work. Can someone please help.
Thanks.
Hitesh.
Avatar of ispaleny
ispaleny
Flag of Czechia image

telnet YourServer 1433
Avatar of arbert
arbert

hmmm, I definately wouldn't enable Netbios over TCPIP.

When you installed MSDE, did you enable the network protocols?  If not, you will only be able to connect to it from the local machine....
Avatar of hiteshas

ASKER

Thanks for the responses.
I have enabled network protocols while installing MSDE. I was able to access this computer from a Windows 2000 Server, but it does not work with Windows 2003.

For me to telnet to the Windows 98 system, do I require anythig to be configured on the Windows 98 system?

Also, I had to use NETBIOS over TCPIP since that was the only way I was able to get the Windows 2003 system to ping the Windows 98 system.. Could you please let me know the reasons why this is not good since I'm unaware of the pitfalls of doing this. Is there a better way to get the Windows 2003 and windows 98 to see each other?

-Hitesh.
NETBIOS is using broadcasting to reach your server by name, or WINS Server.
TCP/IP uses DNS Server for name translation, your problem looks like an incorrectly configured DNS.
Did you try to connect directly using IP address?
Yes. I tried registering Windows 98 MSDE instance using the IP address also. But that too did not work.
ASKER CERTIFIED SOLUTION
Avatar of ispaleny
ispaleny
Flag of Czechia image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
"Also, I had to use NETBIOS over TCPIP since that was the only way I was able to get the Windows 2003 system to ping the Windows 98 system.. Could you please let me know the reasons why this is not good since I'm unaware of the pitfalls of doing this. Is there a better way to get the Windows 2003 and windows 98 to see each other?"


Because of security--not a good idea....

So you could attach with another Windows server (2000).  Do you have SP1 installed on Windows 2003?  Do you have the firewall enabled on 2003?  IP Filtering enabled?
For me to telnet to the Windows 98 system, do I require anythig to be configured on the Windows 98 system?
No. It is a network connector, your keystrokes are send to the server and server output is sent to you back. SQL Server communication is binary, so you see a blank window only. All you need is a correct IP, port number and a free way on firewalls.

Default SQL Server TCP/IP port is 1433, but it can be changed or disabled. You determine the correct port and protocol in svrnetcn.exe utility on the server.
I am not able to telnet to the Windows 98 computer on port 1433. How do I overcome this.
1. Run svrnetcn.exe on Windows 98 machine to see, which network protocols are installed. Enable TCP/IP port 1433.
2. Switch W98 SQL Server to Mixed authentification and restart it.
3. Verify firewall status. There can be multiple firewalls on your client and server both. Even if you don't find any firewall running, there can be network firewalls.
4. If you still are not able to reach the server, use port 80 (HTTP) or 20,21 (FTP) instead of 1433 (Step 1). On the client W2003, run cliconfg.exe and define an alias NewSQLServerAlias of the server on Alias Tab and the new STATIC port (80,...). On W2003 run osql -S NewSQLServerAlias -U YourSQLUserName -P YourSQLPassword  
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
arbert is true, some firewalls parse HTTP/FTP headers and cache requests. This can make SQL request unreadable by SQL Server. Not every firewall is so complex, just try it.
HI Thanks. I shall try this out. The poblem is that the Windows 98 Server is located in a very remote location and it would take 2 days to get there. There is no technical person at that office. They just know how to boot the computer and use Windows Explorer and MS Office. I will tell them over the phone to run the commands and change the ports.
Thanks a lot. This help is really appreciated.
-Hitesh.
Hi. I asked the persons at the Win 98 system site  to execute svrnetcn.exe. But the file did not exist on that system. I tried all I could and has to have some one go down to the site and reinstall their OS (win 98) and reinstall MSDE. Now it worked. I really donot know what was wrong.
Anyways, thanks to all who helped.
I would like to split the points between albert and ispaleny. How do I go about doing that?

-Hitesh