>I have this same problem. My network is TCP/IP only as well. It happens because of the DNS settings in the Networking control panel. Once you log on, your machine checks the DNS server to see if it's there. I'm guessing your DNS server's IP address is 207.168.44.xxx. Since that IP address is outside of your subnet, the router fires off a call. Unfortunetly, there's not a whole lot you can do about it. I tried setting the inactive period shorter so that the router would hang up faster, but then the router would disconnect at inopportune times. So I just live with it!
>
>Sorry I couldn't be more helpful!
>
>>Hi all,
>>
>>This message is not VFP related and I apologize for that. But I don't know where else I could address my demand.
>>
>>I've been using a router for a while to connect to my ISP through an ISDN line. Setup was easy. The only thing is that whenever I log onto the network a router call is triggered. I can verify that the IP address that fired the call is in the range of 207.168.44... I've tried to setup a filter. I'd better call it a plug, because since then nothing passes through and I have to manually trigger the call...
>>
>>Router: D-LINK 106-I
>>Network: TCP/IP only, ervery machine has a fixed address in the range of 192.168.1....
>>
>>José

Gary and Paul,

Some additional info: ervery machine has a fixed address in the range of 192.168.1... The file server is also a DNS with an IP address of 192.168.1.2
Before the router, I used to connect with a modem. I found and deleted the 207.168.44.14. and 207.168.44.15 adresses listed in the Autodial list of Windows NT (by executing RASAUTOU -s from the dot prompt.) but it changed nothing. The only thing I can say, is that I once connecte to these adresses in the past...

José