Unknown ISDN dialup's

[12122053]

Recently my 1604 router dials out to my ISP when i don't want it to. I'm not running no active applications that needs to go out throught my dialer interface. Does anybody know what is causing this? Could i place any access-lists to prevent this thanks. Here is my running config:


founder#sh run
Building configuration...

Current configuration:
!
version 12.0
no service pad
service timestamps debug uptime
service timestamps log uptime
service password-encryption
no service dhcp
!
hostname founder
!
boot system flash
no logging console
enable secret 5
enable password 7 !
!
!
!
ip subnet-zero
no ip finger
no ip domain-lookup
!
isdn switch-type basic-ni
!
!
process-max-time 200
!
interface Ethernet0
ip address 192.68.1.1 255.255.255.0
no ip directed-broadcast
no ip proxy-arp
ip nat inside
!
interface Serial0
ip address 192.68.3.1 255.255.255.0
no ip directed-broadcast
clockrate 2000000
!
interface BRI0
no ip address
no ip directed-broadcast
ip nat outside
encapsulation ppp
dialer rotary-group 1
isdn switch-type basic-ni
isdn spid1 xxxxxxxxxxxxx
isdn spid2 xxxxxxxxxxxxx

interface Dialer1
description connection to ISP
ip address x.x.x.x x.x.x.x
no ip directed-broadcast
no ip proxy-arp
ip nat outside
encapsulation ppp
dialer in-band
dialer idle-timeout 300
dialer string xxxxxxxxxx
dialer load-threshold 3 either
dialer-group 1
no cdp enable
ppp authentication pap callin
ppp pap sent-username xxxxxx password xxxxxxxxxx
ppp multilink
!
ip nat inside source list 1 interface Dialer1 overload
ip classless
ip route 0.0.0.0 0.0.0.0 Dialer1
no ip http server
!
access-list 1 permit 192.68.1.0 0.0.0.255
dialer-list 1 protocol ip permit
banner motd ^C WARNING!!! UNAUTHORIZED USE WILL BE PUNISH, YOU HAVE BEEN WARNED
^C
!
line con 0
exec-timeout 0 0
transport input none
line vty 0 4
password 7 08701E1F5B
login
!
end

founder#disable
founder>exit

Thanks who help.

 

[jeter]

http://www.cisco.com/warp/public/779/smbiz/service/troubleshooting/ts_isdn.htm

Heres a site for trouble shooting isdn on routers. Jeter@LasVegas.com The best answer I could ever give is the one to maintain my Sanity

 

[12122053]

Thanks jeter I think my 2000 server is causing it to dial, but i must do futher testing.

 

[Guest_imported]

Just do a packet sniff, either on the windows 2k box,
or on the device itself (be careful, it will swamp the console)
this should tell you why it has dialled.

Also, setup an enhanced access list to have only the packets you really want going to the internet, and back.
eg, ftp, web, dns, etc
and allow inbound udp, and established tcp

adrian

 

[fireball1]

Had the same problem on a 760. Try
SET PPP Address Negotiation local on
SET ip rip update off
SET ipx rip update off

 

[Guest_imported]

Use a access-list to specify on what condition your has to dial.

Think about wins packets/broadcasts
udp port 137/138 and tcp 139

Peter

 

[Guest_imported]

I'd also try using debug dialer to see what condition is bringing up the interface

 

[NewBoy]

Might not be the same problem, but pplaat suggested something I use for my clients. If you screen out 137, 138 & 139 it prevents NetBIOS packets bringing the line up, which might be what you're seeing given you have a MS n/w.

Also, if memory serves me correctly, debug isdn q931 will give you the source/address of the packets.

Good luck.

 

[croth]

It is more likely to do with WINS DNS and Netbios. Try using an access-list with a time range, have a look at this site.

http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121cgcr/ip_c/ipcprt1/1cdip.htm#22601