Hello, i've recently installed an Omniback client on an Windows NT4, SP5 and everything was working fine. Yesterday i installed the HP VP Internet Services 2.0 on the same system and if i try to add components or upgrade the omniback client e get a timeout, the same timeout i've mentioned in a previous post. No change if i stop the service "HP Internet Services", have to disable it and restart the system, after that omniback installation works again.
Ok, i think the problem must be conflicting ports...i could get no information in wich ports are used in Omniback installation or in Internet Services so does it mean that we can not have VP Internet Services and an Omniback client on the same machine?! somebody knows the ports used during the OB client installation?
Re: VP Internet Services 2.0 and Omniback 3.1 client
Hello, thanks for the quick reply... no much information yet available about Internet Services, i'll wait for that to come out. But, i think port 5555 isn't the only one used in the installation, it is used with comunication between agent and manager, but some other ports must be used during the install, i think...
NetBIOS (137, 138, and 139 TCP) NetBIOS is the protocol used by Microsoft Windows networking to connect LAN clients to file and print servers. NetBIOS will run over IPX, NetBEUI, and TCP.
You should definitely not allow NetBIOS traffic to pass your firewall in either direction. NetBIOS is easily hacked and many exploits exist on hacker Web sites. If you want to link your LANs over the Internet, you should use an encrypted IP tunnel to convey the NetBIOS IP packets through the Internet.
So - Microsoft says DON'T DO IT.
Just for the record - the only function we support through the firewall is the Omniback GUI talking to (controlling) the cell server.
Beyond that you are assuming all of the risks.
Omniback and NT problems? double check name resolution, DNS/HOSTS...