cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
492
Views
0
Helpful
3
Replies

Unable to open webpage through Leased line connectivity and it is with ISDN

sivaram_deevi
Level 1
Level 1

Dear All,

We are facing a peculiar problem we are unable to open a webpage when Site A is connecting to Site B through leased line. But same webpage give output response when it is connected through leased line. The scenario is mentioned below

Site A LAN IP Range : 10.5.249.90

site B address :10.30.248.156

The Ping and traceroute results:

==================================

==========

LEASED LINE

===========

Microsoft Windows 2000 [Version 5.00.2195]

(C) Copyright 1985-2000 Microsoft Corp.

C:\Documents and Settings\Administrator>tracert 10.30.248.156

Tracing route to 10.30.248.156 over a maximum of 30 hops

1 <10 ms <10 ms <10 ms 10.5.249.90

2 31 ms * 31 ms 10.5.250.142

3 46 ms 63 ms 47 ms 10.1.254.13

4 62 ms 63 ms 78 ms 10.1.254.10

5 62 ms 63 ms 78 ms 10.31.250.186

6 62 ms 63 ms 78 ms 10.30.248.156

7 79 ms 78 ms 78 ms 10.30.248.156

8 62 ms 79 ms 78 ms 10.30.248.156

Trace complete.

====

ISDN

====

C:\Documents and Settings\Administrator>tracert 10.30.248.156

Tracing route to 10.30.248.156 over a maximum of 30 hops

1 <10 ms <10 ms <10 ms 10.5.249.90

2 16 ms 31 ms 31 ms 10.5.245.51

3 31 ms 47 ms 31 ms 10.1.254.13

4 47 ms 47 ms 62 ms 10.1.254.10

5 47 ms 63 ms 47 ms 10.31.250.186

6 47 ms 62 ms 63 ms 10.30.248.156

7 47 ms 62 ms 63 ms 10.30.248.156

8 47 ms 78 ms 63 ms 10.30.248.156

Trace complete.

Both are taking same path and response time is sligh varie.

And one more thing we have observed,

Further, when the connectivity is through ISDN and we try to login, we get request timed out during the login time. However, the login process goes through immediately. The ping reply during the login period is given below.

Reply from 10.30.248.156: bytes=32 time=47ms TTL=121

Reply from 10.30.248.156: bytes=32 time=47ms TTL=121

Reply from 10.30.248.156: bytes=32 time=47ms TTL=121

Reply from 10.30.248.156: bytes=32 time=63ms TTL=121

Reply from 10.30.248.156: bytes=32 time=813ms TTL=121

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Reply from 10.30.248.156: bytes=32 time=594ms TTL=121

Reply from 10.30.248.156: bytes=32 time=47ms TTL=121

Reply from 10.30.248.156: bytes=32 time=47ms TTL=121

Reply from 10.30.248.156: bytes=32 time=47ms TTL=121

Reply from 10.30.248.156: bytes=32 time=47ms TTL=121

Reply from 10.30.248.156: bytes=32 time=47ms TTL=121

However, when the connectivity is through Leased Line, and we try to login, the return time increases from 63 ms to around 150 ms. But, the system is not logging in for a long time.

Kindly arrange to provide a solution for our problem.

Regards

Sivarama Krishna

3 Replies 3

thisisshanky
Level 11
Level 11

Do you experience the same problem, from all PCs on the lan or just one. Is there a proxy setting on the PC ??

Sankar Nair
UC Solutions Architect
Pacific Northwest | CDW
CCIE Collaboration #17135 Emeritus

Yes, From all PCs on the lan is facing the same problem. There is no proxy settings on the PC

Hello,

what is the load on the line when you have the connectivity problem ? Can you do a show interfaces and check the tx/rx loads when you experience the problems ? What is the capacity of the leased line ?

Regards,

Georg