network response delay?

taha104 · ‎11-09-2005

Iam using Cisco Pix 501. Whenever i use network commands it get some delay in response. For example if I connect to network drive using net use command i get 4/5 second delay then the commands executes. Or if i open my maped drived it get some delay & then the drive opens. Is there any specific reason why we get these delay?

Thanks in advance

aacole · ‎11-11-2005

Its not possible to give an answer without knowing more about how your network is set up. For instance are you using a VPN to connect to the network drive, do you use DNS (or WINS) to refer to drive?

So many factors could cause a delay, can you give more detail?

taha104 · ‎11-11-2005

No iam not using VPN.Iam connecting directly to my network which uses DNS for name query. Ours is pure IP network with windows 2003 server DHCP/DNS/Domain Controller. All the switches, routers, Network cards are on Gagabit capacity. Below is the configuration of my firewall:

PIX Version 6.3(4)

interface ethernet0 auto

interface ethernet1 100full

nameif ethernet0 outside security0

nameif ethernet1 inside security100

enable password 8Ry2YjIyt7RRXU24 encrypted

passwd 2KFQnbNIdI.2KYOU encrypted

hostname pixfirewall

domain-name towson.edu

fixup protocol dns maximum-length 512

fixup protocol ftp 21

fixup protocol h323 h225 1720

fixup protocol h323 ras 1718-1719

fixup protocol http 80

fixup protocol rsh 514

fixup protocol rtsp 554

fixup protocol sip 5060

fixup protocol sip udp 5060

fixup protocol skinny 2000

fixup protocol smtp 25

fixup protocol sqlnet 1521

fixup protocol tftp 69

names

pager lines 24

mtu outside 1500

mtu inside 1500

ip address outside dhcp setroute

ip address inside 192.168.1.1 255.255.255.0

ip audit info action alarm

ip audit attack action alarm

pdm logging informational 100

pdm history enable

arp timeout 14400

global (outside) 1 interface

nat (inside) 1 0.0.0.0 0.0.0.0 0 0

timeout xlate 0:05:00

timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h225 1:00:00

timeout h323 0:05:00 mgcp 0:05:00 sip 0:30:00 sip_media 0:02:00

timeout uauth 0:05:00 absolute

aaa-server TACACS+ protocol tacacs+

aaa-server TACACS+ max-failed-attempts 3

aaa-server TACACS+ deadtime 10

aaa-server RADIUS protocol radius

aaa-server RADIUS max-failed-attempts 3

aaa-server RADIUS deadtime 10

aaa-server LOCAL protocol local

http server enable

http 192.168.1.0 255.255.255.0 inside

no snmp-server location

no snmp-server contact

snmp-server community public

no snmp-server enable traps

floodguard enable

telnet timeout 5

ssh timeout 5

console timeout 0

dhcpd address 192.168.1.2-192.168.1.129 inside

dhcpd lease 3600

dhcpd ping_timeout 750

dhcpd auto_config outside

dhcpd enable inside

terminal width 80

Cryptochecksum:6c88a0676ddd60cb381e97cf1583e87d

: end

jackko · ‎11-11-2005

please excuse me for misunderstanding.

assuming you were establishing the connection directly to the server, i.e. traffic with the same lan segment; pix doesn't involve at all.

for lan traffic, the pc will arp and send packet directly to the server, it won't forward the packet to the pix and then from the pix to re-route the packet back to the server.