Anonymous_User Absent Member.
Absent Member.
1782 views

Cannot access server through web interface

I have an NW 6.0 SP4 server at a remote site that's connected by a dedicated
T1. A couple of months ago I rebooted it. Since then, I have not been able
to access it via IE which I have been doing for the past two years. I've
rebooted a few times before with no problems. Ideas as to what I should
look at?

Thanks.


Labels (2)
0 Likes
5 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Cannot access server through web interface

If you load TCPCON on the server, go to Protocol, TCP, and choose the
default.

You might have to hit tab to see the port numbers, which of the
following ports are being listened to? These are not necessarily in
order, so check the whole list:

80
81
389
443
524
636
2200
2211
8008
8009
51080
51443
52080
52443

Just add a yes or no after each port.


--
Timothy Leerhoff
Novell Support Forum Volunteer Sysop

"I have the body of a god,
Unfortunately it's Buddha."
- quote from a t-shirt
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Cannot access server through web interface

I'm going to that site on 9-29-05 so I will check when I'm up there (it's 50
miles away). I will post back when I find something out.

Thanks.

"Timothy Leerhoff" <tleerhoffNO@SPAMqwest.net> wrote in message
news:tri_e.2069$jT.1880@prv-forum2.provo.novell.com...
> If you load TCPCON on the server, go to Protocol, TCP, and choose the
> default.
>
> You might have to hit tab to see the port numbers, which of the
> following ports are being listened to? These are not necessarily in
> order, so check the whole list:
>
> 80
> 81
> 389
> 443
> 524
> 636
> 2200
> 2211
> 8008
> 8009
> 51080
> 51443
> 52080
> 52443
>
> Just add a yes or no after each port.
>
>
> --
> Timothy Leerhoff
> Novell Support Forum Volunteer Sysop
>
> "I have the body of a god,
> Unfortunately it's Buddha."
> - quote from a t-shirt



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Cannot access server through web interface

k, I will be away for a week starting Oct2, if you post after that I
suggest you start a root posting with the port listing, this way you
should get an answer a bit quicker.

--
Timothy Leerhoff
Novell Support Forum Sysop
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Cannot access server through web interface

Matt wrote:
> I'm going to that site on 9-29-05 so I will check when I'm up there (it's 50
> miles away). I will post back when I find something out.
>
> Thanks.
>
> "Timothy Leerhoff" <tleerhoffNO@SPAMqwest.net> wrote in message
> news:tri_e.2069$jT.1880@prv-forum2.provo.novell.com...
>
>>If you load TCPCON on the server, go to Protocol, TCP, and choose the
>>default.
>>
>>You might have to hit tab to see the port numbers, which of the
>>following ports are being listened to? These are not necessarily in
>>order, so check the whole list:
>>
>>80
>>81
>>389
>>443
>>524
>>636
>>2200
>>2211
>>8008
>>8009
>>51080
>>51443
>>52080
>>52443
>>
>>Just add a yes or no after each port.
>>
>>
>>--
>>Timothy Leerhoff
>>Novell Support Forum Volunteer Sysop
>>
>>"I have the body of a god,
>> Unfortunately it's Buddha."
>>- quote from a t-shirt

>
>
>

Just run a port scanning tool. Ports 8008,8009, are the defaults for
httpstk and portal services. Note these must be loaded in the
autoexec.ncf, if they are it is usually a certificate issue.
Lots of tids on fixing that. pkidiag can help you determine problems
first without alterations.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Cannot access server through web interface

I went through TCPCON as stated below and port 8009 was not listed. I ran
PKDIAG and it said the certificate had expired. I had it reinstall the
certificate, rebooted the server and I was able to access the server via
Remote Manager. Thanks for all the help.

"Drum Dude" <jgover@rogers.com> wrote in message
news:pwx_e.2683$jT.796@prv-forum2.provo.novell.com...
> Matt wrote:
> > I'm going to that site on 9-29-05 so I will check when I'm up there

(it's 50
> > miles away). I will post back when I find something out.
> >
> > Thanks.
> >
> > "Timothy Leerhoff" <tleerhoffNO@SPAMqwest.net> wrote in message
> > news:tri_e.2069$jT.1880@prv-forum2.provo.novell.com...
> >
> >>If you load TCPCON on the server, go to Protocol, TCP, and choose the
> >>default.
> >>
> >>You might have to hit tab to see the port numbers, which of the
> >>following ports are being listened to? These are not necessarily in
> >>order, so check the whole list:
> >>
> >>80
> >>81
> >>389
> >>443
> >>524
> >>636
> >>2200
> >>2211
> >>8008
> >>8009
> >>51080
> >>51443
> >>52080
> >>52443
> >>
> >>Just add a yes or no after each port.
> >>
> >>
> >>--
> >>Timothy Leerhoff
> >>Novell Support Forum Volunteer Sysop
> >>
> >>"I have the body of a god,
> >> Unfortunately it's Buddha."
> >>- quote from a t-shirt

> >
> >
> >

> Just run a port scanning tool. Ports 8008,8009, are the defaults for
> httpstk and portal services. Note these must be loaded in the
> autoexec.ncf, if they are it is usually a certificate issue.
> Lots of tids on fixing that. pkidiag can help you determine problems
> first without alterations.



0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.