I found my problem! You were right, Al was right, Charlie was right, and so was I!
My test system was a Win98 notebook. The installation must have gone awry as I have now re-installed on another Win98 as well as a Win95 pc and I can connect using tcp/ip just fine. The first check I made was to vsee if netstat reports port 1433 listening and it did. Where on the notebook port 1433 was not listed. I knew that was my problem. Thanks to everyone for the help.
-Isaac
>>>>I have been experimenting with MSDE. Its a very nice!
>>>>Running as a service on an NT box works fine.
>>>>Running as a service on a Win98 box worked locally but I cannot create an odbc connection the Win98 pc from another pc.
>>>>I can ping the Win98 pc and even map a drive to it, so its not necessarily a networking issue. At least not an obvious one to me. Does anyone know if this should possible? If so what might be the trick?
>>>>
>>>>Thanks,
>>>>-Isaac
>>>
>>>
>>>You should be using TCPIP protocol not the NAMED PIPES. The latter one is for NT OS only. I been using both MSDE and SQL Server 7.0. both runs in WIN95/98 platform.
>>
>>Hello Jess,
>>
>>You are correct. I was able to find that by default SQL Server is configured for named pipes which is not supported on Win9x. Also by default MSDE is expecting to use tcp/ip port 1433. When I run netstat on the Win98 pc I notice that there is no tcp port listening on port 1433. Could this be my problem?
>>Did you have to configure your Win9x pc in any special way?
>>
>>Thanks,
>>-Isaac
>
>Sorry for the delay. Our internet server was downed 12 hours.
>
>When you try to create System DSN, you should click the Client Configuration button to change the protocol from named pipes to TCP/IP.
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only