Connection refusal using Reflections, Clarification my difficulty

[David A. Ramsey]

Sorry if I am not entering this followup question properly. This is my first subject listing on the forum and I am having difficulty determining the details of the workings of the forum.

My earlier question had to do with connection difficulties to HP3000.

The heirarchy of communication is from Office PC to Office Network, to Cable model in the office, to internet fireward URL for clearance with password, to HP3000 server running company network.

The proceedure to sign on is to connect to Firewall access using Net Work administrator provided password, then with Firewall clearance running in the background Relections is opened and connection URL entered using VT-MGR network.

The error message received is "General Connection Failure".

As stated before this connection worked for about 3 months without incident.

No changes were made at the office to any of these programs before the problem reared its ugly head.

In an effort to correct the problem Reflections version was changed from 5 to 7 and setup reset.

At the suggestion of HP3000 network tech support I successfully pinged the server showing connectivity was valid.

During this troubleshooting process it was determined that connection can be made using an alternate dial up connection in the office.

Network technical support and IP support all deny knowledge of any changes that have been made that should cause this connection problem and in effect are saying it is not a problem with my system it must be someone elses problem.

My responsibility is to keep the office connected but I don't know where to go from here.

[paul courry]

Let's try a couple of things.........

1. Fire up Reflection.
2. Go into Connection Setup
3. Select NETWORK/VT-MGR, under Host Name type in the IP address of the HP3000 computer. Check it with NMMGR.
4. Hit Connect.

This will give you a VT-MGR connection to the specific IP address you typed in.

If you get a general connection failure then bring in the network people, have them throw a sniffer on it and check out what is being transmitted back and forth, step by step.

Also suggest you double check the HP's IP address both by NSLOOKUP and by checking NMMGR, then ping the sucker from your PC.