Re: Open Ports
- From: Todd <Todd@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 11 Feb 2008 04:32:00 -0800
Andrew, What I found out was, I uninstalled the program and reinstalled it.
Seems to be working now. I don't think its a very stable program though.
"Andrew Meador" wrote:
On Jan 14, 1:08 pm, Todd <T...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:.
The client software works on the server ok, full mode there. But why do they
want the ports open even ifs all in house and behind the hardware firewall???
"Andrew Meador" wrote:
On Jan 14, 11:25 am, Todd <T...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
The security key is plugged into the server and the workstations need to see
it for the software that needs it on the workstations to open up in normal
mode not demo mode. HASP is the security key maker but its for a clock
software and a work clock. If the software on the workstations do see the
key, it opens up in demo mode. The clock place is trying to tell me it in my
network not there software. The only thing between the work stations and the
server is Cisco Catalyst Express 500 switches for voice over IP. I think its
a software issues.....
"Andrew Meador" wrote:
On Jan 14, 10:17 am, Todd <T...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
On a new install of Windows Sever 2003, and firewall not yet setup, are only
certain ports open?? I'm trying to get a usb security key to work so I can
see it on the server from workstations. Do I have to start the firewall in
Windows Server and open the ports I want such as 3047, 1974 even though the
workstations are behind the hardware firewall?
If you are able to connect directly to the server (without going
through a router/firewall) and the server has no firewall running, you
should be able to connect. How are you trying to connect? Terminal
services/Remote desktop?
If you are passing through a router/firewall you will need to open/
forward proper ports to the server from within the router.
Andrew- Hide quoted text -
- Show quoted text -
How does the key connect to the server?
How does the software on the workstations know where to find the
key, is there somewhere where you can configure that? Is there some
"agent" on the server that should be finding the key and accepting
requests from the workstations based on a good key being plugged in?
What I'm trying to get at is whether this may be a configuration
issue. From my experience, software on the machine where these kinds
of keys are plugged in are the ones that can see the key, not other
machines. Typically this allows a central component on the 'server'
machine to work (like the timeclock management module) and that module
will take requests from the clients. The central component then
decideswhat level of operation is permissable (full/demo/etc...) If
the key is a usb device and is showing up as a drive, maybe the usb
drive needs to be shared, and the clients software configured to
connect to the share. If network based, clients need IP address and
port of key device? If on a serial or LPT port, I don't know - the
only thing I could think of here is that you would have the central
management structure. Again in this case, maybe the clients need
configured with settings on how to connect to the 'agent', for that
you may need IP/computer name, possibly a port number, and maybe the
'agent' name for it to connect to the 'agent' component.
Have you tried running the client software on the server to see if
it is able to work in full mode there? If not, maybe the key is bad/
corrupt?
Andrew- Hide quoted text -
- Show quoted text -
Well, if the client software works ok when running directly on the
server; it is supposed to run in this structure (clients connecting to
server 'agent' on some specified ports); and there are no firewalls
between the server and clients... it should work. You mentioned 2
ports, is this the actual ports they want open? Typically
communication is done one way through one port in a scenario like
this, but if they are asking for 2 ports, maybe they are using them
for inbound/outbound, or in other words, maybe one port needs to be
open on the server (which should not be an issue since you havn't
installed the firewall there yet) to allow the client to comminicate
with the server 'agent', but maybe the other port is to be open on the
client so the server can initiate communications with an 'agent'
client? If this is the case, maybe it is not the server that is
causing the problem, but the clients. Do they have firewalls running?
If so, try turning the firewall off on one of these test clients to
see if that works. If so, you're on step closer, then you'll just have
to figure out which port needs open on which end.
Let me know what you find out.
Andrew
- Prev by Date: Re: Two NICs
- Next by Date: Re: computer name change affect profiles?
- Previous by thread: Paging file size for a 16gb memory server.
- Next by thread: Extending a partition with unallocated space...
- Index(es):
Relevant Pages
|
