|
|
What port settings does EA/V use with & without firewalls? |
|
|
The description below shows the behavior of EA/V when firewall settings are in place. It is also applicable when firewall settings are not in use.
This is how it works when connecting to a Microsoft Windows NT workstation:
1. Set the firewall settings to 4440 -> 4443 (4 ports).
2. Connect to a Windows NT host.
3. The PC listens on 4440 for the host call back, and sends the vpdata request to servd from 4441 to 1645.
0007 00:00:00 ...TD Ncdm: Listening (backlog=1) on port 4440...
0008 00:00:00 ..Started daemon on port 4440
0009 00:00:00 ...TC Nclient: SockCreate(monument.fortel.com, 1645)
0010 00:00:00 ...TC Nclient: socket #508 port 4441 (Rcv=32767 Snd=32767)
0018 00:00:00 ..Asking 'monument.fortel.com' to call '198.242.57.39' back on port 4440 for 'monument.fortel.com' data
4. A second connection to the same host uses the next set of ports (4442 and 4443):
0006 00:00:00 ...TD Ncdm: socket #540 port 4442 (Rcv=32767 Snd=32767)
0007 00:00:00 ...TD Ncdm: Listening (backlog=1) on port 4442...
0008 00:00:00 ..Started daemon on port 4442
0009 00:00:00 ...TC Nclient: SockCreate(monument.fortel.com, 1645)
0010 00:00:00 ...TC Nclient: socket #632 port 4443 (Rcv=32767 Snd=32767)
5. A third connection to the same host rolls back to the beginning of the set:
0006 00:00:00 ...TD Ncdm: socket #172 port 4440 (Rcv=32767 Snd=32767)
0007 00:00:00 ...TD Ncdm: Listening (backlog=1) on port 4440...
0008 00:00:00 ..Started daemon on port 4440
0009 00:00:00 ...TC Nclient: SockCreate(monument.fortel.com, 1645)
0010 00:00:00 ...TC Nclient: socket #608 port 4441 (Rcv=32767 Snd=32767)
Because the 4441 => 1645 connection is not is use, it works fine on Windows NT. When you do a netstat on the PC, you will see only the connected sessions:
TCP 198.242.57.39:4440 198.242.57.25:2440 ESTABLISHED
TCP 198.242.57.39:4440 198.242.57.25:2623 ESTABLISHED
TCP 198.242.57.39:4442 198.242.57.25:2566 ESTABLISHED
|
|