Path: newssvr20.news.prodigy.com!newsmst01.news.prodigy.com!prodigy.com!news.linkpendium.com!nntp-relay.ihug.net!ihug.co.nz!nntp.cs.ubc.ca!newsfeed.stanford.edu!postnews1.google.com!not-for-mail From: vslabs@onwe.co.za (Billy Verreynne) Newsgroups: comp.databases.oracle.server Subject: Re: Lost Oracle connectivity Date: 6 Jul 2003 22:40:23 -0700 Organization: http://groups.google.com/ Lines: 35 Message-ID: <1a75df45.0307062140.3ae9b22f@posting.google.com> References: NNTP-Posting-Host: 198.54.206.91 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: posting.google.com 1057556423 9847 127.0.0.1 (7 Jul 2003 05:40:23 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: 7 Jul 2003 05:40:23 GMT Xref: newssvr20.news.prodigy.com comp.databases.oracle.server:237034 "Ramon Mendiguren" wrote .. > We have been working with Oracle 8.1.7.0.0 (Windows 2000 advance server) and > a client (Win 2000 Pro). This two computer where in a NT Domain. This > weekend we have put them in a Win 2000 domain, and in that moment the server > and the client has lost the connection. Our new domain is "cikautxo.es". Can be any number of things. What is the _exact_ error message you get? A couple of things come to mind. Domain authentication (does the client has the required privs to access services on the domain controller?). OS Authentication (is the Oracle instance configured for that?). Is the listener service running? What does the Microsoft (poor) implementation of iptables say (check if you do not have that active and if active, what ports and IPs are being blocked). And oh yes.. is TCP/IP even installed? You can run Microsoft's Domain Networking on IPX/SPX and NetBIOS as far as I know - both these support NetBEUI and that's all that's needed for the domain part to work.. What really bugs me.. consider it a rant and don't take it personal.. just how many so-called techies of today can not solve problems. Hell, that is what being techie is al about. Instead of determining which components are involved in the error chain (software, drivers, protocols, network, etc) and testing each of these in turn to see where the problem occurs... the new age techie wets his pants and pull his hair and moans "why me?". A simple ping from client to server and one from server to client would have made sure that there's IP connectivity. Just how hard is it to get a few neurons to come up with that? -- Billy