[omniORB] RE: Unable to contact naming service.

Sat, 9 Jan 1999 06:40:07 -0700

This is a multi-part message in MIME format.

------=_NextPart_000_0046_01BE3B9A.E5A12C20
Content-Type: text/plain;
	charset="windows-1250"
Content-Transfer-Encoding: quoted-printable

I have now finally been able to establish a
connection to the naming service on a standalone Windows-95 system =
without a network interface card.
This required that dialup networking (DUN) be up
and running (which connects to my ISP) before
omninames is started - and DUN not then stopped.
Any suggestions on how to get around this ?

------=_NextPart_000_0046_01BE3B9A.E5A12C20
Content-Type: text/html;
	charset="windows-1250"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>

<META content=3D"text/html; charset=3Dwindows-1250" =
http-equiv=3DContent-Type>
<META content=3D'"MSHTML 4.72.3110.7"' name=3DGENERATOR>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT color=3D#000000 face=3D"Courier New" size=3D3>I have now =
finally been able=20
to establish a</FONT></DIV>
<DIV><FONT color=3D#000000 face=3D"Courier New" size=3D3>connection =
</FONT><FONT=20
color=3D#000000 face=3D"Courier New" size=3D3>to the naming service on a =
standalone=20
Windows-95 system without a network interface card.</FONT></DIV>
<DIV><FONT color=3D#000000 face=3D"Courier New" size=3D3>This required =
that dialup=20
networking (DUN) be up</FONT></DIV>
<DIV><FONT color=3D#000000 face=3D"Courier New" size=3D3>and running =
(which connects=20
to my ISP) before</FONT></DIV>
<DIV><FONT color=3D#000000 face=3D"Courier New" size=3D3>omninames is =
started - and=20
DUN not then stopped.</FONT></DIV>
<DIV><FONT color=3D#000000 face=3D"Courier New" size=3D3>Any suggestions =
on how to=20
</FONT><FONT color=3D#000000 face=3D"Courier New" size=3D3>get around =
this=20
?</FONT></DIV>
<DIV><FONT color=3D#000000 face=3D"Courier New"=20
size=3D3></FONT>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_0046_01BE3B9A.E5A12C20--