Netscape 2.0 B4 Will not talk to server.
Peter Baasch
>Bodine wrote:
> = : win 95, ns 2.0b4 [Twinsock]
> = : Try connecting again later, or try restarting netscape. You may also
> = : try restarting windows.
> = : Why is this happening to me?
>how...@cuug.ab.ca wrote:
> = EXACT same thing happens to me. Is it because Tumpet 2.0B ain't
> = workin' with this latest beta? Every browser has worked fine until this
> = one! 8)
>Twinsock doesn't work. Trumpet Winsock doesn't work. And I'm using
>Twinsock and get a different error message -- the one about not being
>able to locate the url -- such as Netscape's home page (!) Happens with
>ALL urls I try, not just the ones that are likely to be busy, and which
>indeed are NOT busy for my other machine (486, 3.1, Twinsock, beta4a).
>Win95 makes 3.1 look good. Who'd have thought it?
Nearly the same happened to me with Windows-NT-3.51 (SP2):
Netscape 1.22 has worked fine. Then I installed Netscape 2.0b4 in an
other directory and got the error messages, on BOTH versions.
I deleted both and reinstalled 1.22, but the problem is still there.
/##########==========------------------------------==========##########\
| P e t e r B a a s c h |
| Technische Universit"at Hamburg-Harburg // TI 5 // Telematik |
| Martin-Leuschel-Ring 16; 21073 Hamburg; Germany |
| http://www.ti5.tu-harburg.de/staff/baasch (Fax) +49/40/7718-2581 |
| mailto:baa...@tu-harburg.d400.de (Phone) +49/40/7718-3379 |
\##########====>FC ST.PAULI --- You'll never walk alone!<====##########/
[paul lew]
: bas...@cello.gina.calstate.edu wrote:
:
: : Bodine wrote:
: : = : win 95, ns 2.0b4 [Twinsock]
: : = : Try connecting again later, or try restarting netscape. You may also
: : = : try restarting windows.
: : = : Why is this happening to me?
:
: : how...@cuug.ab.ca wrote:
: : = EXACT same thing happens to me. Is it because Tumpet 2.0B ain't
: : = workin' with this latest beta? Every browser has worked fine until this
: : = one! 8)
:
: : Twinsock doesn't work. Trumpet Winsock doesn't work. And I'm using
: : Twinsock and get a different error message -- the one about not being
: : able to locate the url -- such as Netscape's home page (!) Happens with
: : ALL urls I try, not just the ones that are likely to be busy, and which
: : indeed are NOT busy for my other machine (486, 3.1, Twinsock, beta4a).
:
: : Win95 makes 3.1 look good. Who'd have thought it?
:
: Nearly the same happened to me with Windows-NT-3.51 (SP2):
: Netscape 1.22 has worked fine. Then I installed Netscape 2.0b4 in an
: other directory and got the error messages, on BOTH versions.
: I deleted both and reinstalled 1.22, but the problem is still there.
Glad I'm not the only one!!! Found that mosaic 2.0 for nt 3.51 also
has the same sort of problem in not connecting/recognizing the ppp
connected modem.
Jonathan J Quick
> Nearly the same happened to me with Windows-NT-3.51 (SP2):
> Netscape 1.22 has worked fine. Then I installed Netscape 2.0b4 in an
> other directory and got the error messages, on BOTH versions.
> I deleted both and reinstalled 1.22, but the problem is still there.
I'm using Netscape 2.0b4 with NT Workstation 3.5 with no problems.
This post was input with the Netscape 2.0b4 newsreader window. The
mailer works fine as well. I'm connecting through RAS and the NT
TCP/IP service using PPP.
JJ.
[paul lew]
Please note that person is using 3.51 with sp2; I also have a problem
with netscape 2.0b4 with my nt workstation 3.51 and sp3. I also have
tried mosaic and it also doesn't work.
Looks like ms changed something between 3.5 and 3.51 to kill apps; any
hints?
Nik Belajcic
be commenting on the wrong issue. However, it seems to
resemble my problem with Netscape when I changed from NT3.5 to
3.51. Under 3.5 everything worked fine. When I installed 3.51
(set-up upgrade) Netscape no longer worked. I could login to
my service provider but Netscape was totally deaf to any URL I
would give it. I tryed reinstalling 3.5 and again it worked
fine. Apply 3.51 ugrade and it stops working. After several
weeks of talking to modem manufacturers, trying newer versions
of modem.inf file and talking to Microsoft the problem still
did not go away. Finally, I simply removed both RAS and TCP/IP
services in my 3.51 installation and reinstalled them - and
what do you know???!!! It all of the sudden started to work.
I haven't got service packs yet so I do not know if it was a
bug addressed in in one of them. It's still a bit of a mystery
but at least now it works.
Nik Belajcic.
mr...@escape.ca
For 32 bit Netscape -
You need to go into ther registry and edit the following:
HKEY_LOCAL_MACHINE_SOFTWARE_Microsoft_Windows_CurrentVersion_AppsPath
Delete the references to netscape.exe and naplayer.exe, this is a known fix.
If you are Netscape 16 bit try renaming your netscape executable something other
than netscape.exe.
Hope this helps.
baa...@tu-harburg.d400.de (Peter Baasch) wrote:
>bas...@cello.gina.calstate.edu wrote:
>>Bodine wrote:
>> = : win 95, ns 2.0b4 [Twinsock]
>> = : Try connecting again later, or try restarting netscape. You may also
>> = : try restarting windows.
>> = : Why is this happening to me?
>>how...@cuug.ab.ca wrote:
>> = EXACT same thing happens to me. Is it because Tumpet 2.0B ain't
>> = workin' with this latest beta? Every browser has worked fine until this
>> = one! 8)
>>Twinsock doesn't work. Trumpet Winsock doesn't work. And I'm using
>>Twinsock and get a different error message -- the one about not being
>>able to locate the url -- such as Netscape's home page (!) Happens with
>>ALL urls I try, not just the ones that are likely to be busy, and which
>>indeed are NOT busy for my other machine (486, 3.1, Twinsock, beta4a).
>>Win95 makes 3.1 look good. Who'd have thought it?
>Nearly the same happened to me with Windows-NT-3.51 (SP2):
TJoeO
>In <30EEC6...@dircon.co.uk>, Jonathan J Quick <jjq...@dircon.co.uk> writes:
>: Peter Baasch wrote:
>:
>: : Nearly the same happened to me with Windows-NT-3.51 (SP2):
>: : Netscape 1.22 has worked fine. Then I installed Netscape 2.0b4 in an
>: : other directory and got the error messages, on BOTH versions.
>: : I deleted both and reinstalled 1.22, but the problem is still there.
>:
>: I'm using Netscape 2.0b4 with NT Workstation 3.5 with no problems.
>: This post was input with the Netscape 2.0b4 newsreader window. The
>: mailer works fine as well. I'm connecting through RAS and the NT
>: TCP/IP service using PPP.
>:
>: JJ.
>Please note that person is using 3.51 with sp2; I also have a problem
>with netscape 2.0b4 with my nt workstation 3.51 and sp3. I also have
>tried mosaic and it also doesn't work.
>Looks like ms changed something between 3.5 and 3.51 to kill apps; any
>hints?
I have Netscape 2.0b3 on my computer at work and everything works
great (as great as you can at 14.4) but at home when I installed NS
2.0b4 I started getting no connections at all. Tried upgrading
yeaterday to NS 2.0b5 and nothing has changed!!!
When I try to connect to ANY server I quickly get the somewhat common
message on almost every server:
Network error occurred: unable to connect to server. The server
must be down or unreachable. etc.
But if I try to connect to www.microsoft.com (I have no idea why them
but is is continually repeatable) I get a new message from that point
on:
Netscape was unable to create a socket connection. Ther may be
insufficient system resources or the network may be down.
(Reason: not enough memory). Try connecting again later or
try restarting Netscape. You can also try restarting
Windows.
I have a 486 w/ 8 megs and my PCTools (at the time of message says
that I have 52% free system resources, 55% free GDI resources, and 52%
free user resources. That seems like enough.
Help!!!!!
TJoeO
Robert Ford
removed the interface it worked fine.
robo
Allen K. Smith
Ever since I installed sp3, netscape 2.0b[3-5] cannot resolve most hostnames.
IP addresses work fine.
Occasionally it will work once to an address. It seems to work if our local
DNS server has not cached the name, but this is sporadic. Bizarre.
All my other 16 and 32 bit winsock apps work fine.
sigh
Allen Smith
laz...@ico.com
mike
: I got this with NT 3.51 WS after I installed the 95 beta interface. When I
: removed the interface it worked fine.
I run NT Server 3.51... I too ran Netscape 2.0b5 without any problems
until I upgraded to the new shell.. Then I started getting socket errors...
Is there a fix for this? I really enjoy the new shell, but because my NT
server is a web server, I *really* need Netscape to run locally..
PLEASE e-mail me if you've heard any patches for this!
--mike
Miami Al
the problem please e-mail me as I have tried forever to get it working.
here's hopeing,
mia...@aol.com
Phil Sphicas
If you try to run the 32-bit version of Netscape Navigator (1.x or 2.0)
on a Windows NT system with the "Windows 95 Shell Preview" ("NewShell")
installed, you will get this error as soon as Netscape Navigator starts up:
Netscape was unable to create a network socket connection. There
may be insufficient system resources or the network may be down.
(Reason: Invalid argument)
Try connecting again later or try restarting Netscape. You can also
try restarting Windows.
To solve this, go into the Windows NT registry by running "regedt32",
then go to this section:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\App Paths
Delete the entries there for NETSCAPE.EXE, NAPLAYER.EXE, and any other
applications which have trouble with NewShell.
You should now be able to run Netscape Navigator under NewShell without
any trouble.
When I followed the steps here, I got 1.22 working again, but 2.0b6 still
wouldn't go. But who knows.. maybe it'll work for some of you. Good luck!
-phil sphicas
(psph...@hmc.edu)
Terry Harris
and nescape is aware.
--
\\\|///
\\ - - //
( @ @ )
_/_/_/_/_/_/_/_/_/_/_/_/oOOo-(_)-oOOo_/_/_/_/_/_/_/_/_/_/_/_/
_/ _/
_/ Terry Harris _/
_/ _/
_/ tha...@dial.pipex.com _/
_/ Life Begins at Zero _/
_/ _/
_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/Oooo_/_/_/_/_//_/_/_/_/_/_/_/
oooO ( )
( ) ) /
\ ( (_/
\_)