Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Groupwise remote client can not connect to server

Status
Not open for further replies.

PIPIL

MIS
Jul 15, 2003
57
US
Hello all!
here is the story: we have groupwise 5.5 users they connect remotely using webaccess and using the client over the internet, a consultant came over to change all the passwords in the server because our Main network admin was fired and the VPs were afraid he could do damage to our netwok. after that which we don't know if that was the cause of the problem, but the Groupwise client remote using the internet is not working any more. we can not seems to ping that IP address or the domain name from the internet which is something like wise.xxxxx.com the webaccess portion works normal even the inhouse groupwise works normal.
we have Esafe(different server win 2k server) as our email filtering software and we have checkpoint(Appliance with a Win2k Pro workstation)so does anybody know this is happening?
is the password changing can cause this?
we have Netware 5.1.nds version 8.79

Thank you for your help.
 
The GW remote client should (or can) produce a log which will help isolate the problem. It should show whether you are failing to connect or failing to authenticate. You could create a brand new GW account and set up GW remote to access that account to make sure the connections work. If the connections don't work, take a look at your firewall. You need specific ports open to allow GW remote to talk with the server.
 
Your ports for the GroupWise client is 1677, make sure the consultant didn't block out this port through your firewall. Your inability to ping the ip address may be that the firewall is set to drop ICMP packets, if this is the case you can still connect over tcp on port 1677 to the server but you'll not be able to ping the address.

As rjs also stated, it also good to check the server log, there may be attempts to log into the PO but fail to authenticate.



david e
*end users are just like computers, some you can work with...others just need a simple reBOOTing to fix their problems.*
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top