nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

iwproxy unable to connect

Nicholas

Hello,

I have installed the TeamSite6.5 but getting following error, please suggest for solution

iwproxy was unable to open a connection to: 192.168.1.1:81
Reason: No error.

Thanks Nicholas

Find more posts tagged with

Comments

gzevin

have you installed any webservers on that port already? It's a common issue if the servers fight for a port (iwproxy as an apache instance, in fact).

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

Migrateduser

Whichever your platform, do a "netstat -an" and see if there's something already listening on port 81. If so and you're not able to determine if it's Teamsite, kill all IW services and run the command again.

Dave

Current Environment(s):
(1) TS 6.1 SP2 on W2K3
(2) TS 6.1 SP2 on W2K
(3) TS 6.1 on W2K

Nicholas

Yeah, I have IIS installed. Please lemme know if you want any more information

***

I checked netstat -an, there is nothing running on port 81

-- Nicholas

Edited by Nicholas on 03/15/05 05:29 AM (server time).

gzevin

the port IIS is running should match customer_webserver (or something like that) in iw.cfg

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

Nicholas

Yes, matching

gzevin

try to restart IIS

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

nipper

what happens when you open a browser to

http://192.168.1.1:81/

?

Nicholas

while http://192.168.1.25:81/ in browser it's giving following message

Under Construction
The site you were trying to reach does not currently have a default page. It may be in the process of being upgraded.
Please try this site again later. If you still experience the problem, try contacting the Web site administrator.

Edited by Nicholas on 03/15/05 08:48 PM (server time).

nipper

>http://192.168.1.25:81/

OK, but why is iwproxy trying to go to
http://192.168.1.1:81/ ??????

Check your web server settings in iw.cfg I think you used the wrong IP address

gzevin

true..

the entry for customer webserver in iw.cfg need to be cross-checked... I think so..

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU