- A host left a Netscape open but not borwsing.
- A host with an application to the Internet left open, such
as PCN (PointCast), PING, ftp...etc.
- A Win95 or NT host with an incorrect IP address or netmask setup
(NetBUI broadcast packets will be sent to Prestige and cause Prestige to outcall.)
- A workstation with wrong domain name setup or wrong Domain Name
Server IP address setup.
- A host with incorrect IP address or subnet setup.
- Go to SMT Menu 24.1
- Stop all the Internet Access application
- Clear all the counters and packet triggered the call field, and let the system sit
still.
- When the call is triggerred by some unknown reason, then you can see which type
of packet that trigger the call. If it is IP, then you can tell which station sends the
packet.
- First make sure the Type is IP.
- Check the protocol field ( bold in above example ):
0x01: ICMP
0x06: TCP
0x11: UDP
- Check which station trigger the outcall ( underline numbers in above example )
CC F7 CB B4
|
204.247.203.180 is the IP address of the workstation
that triggered the outcall.
This is the source address in the packet |
CC D9 00 02
|
204.247.203.180 is the IP address of the workstation
that triggered the outcall.
This is the destination address in the packet. |
( Note: you can use 'nslookup' in Unix to verify who
204.217.0.2 is! )
|
NetBIOS-Filter
The following filters prevent, that a NetBIOS Call
(Broadcast) on the network triggers a connection with the Internet.
* Enter the number of the NetBIOS Filter at this position
Troubleshooting Example
The Zyxel Prestige Router opens a connection every minute, but nobody is
using the Prestige.
Verify which process or services triggers the call.
In the Menu 24.1 we find, that the workstation 192.168.136.10 triggers a
SQL*NET call to the workstation 193.72.194.28.
In the Menu 24.1 we find, that the workstation 192.168.136.11 triggers a
NetBIOS call to the workstation 193.72.194.134.
|