Closed Bug 143388 Opened 23 years ago Closed 23 years ago

Time out errors on Indus server for first time visit

Categories

(SeaMonkey :: General, defect)

x86
Windows NT
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: deepakdaniel, Assigned: deepakdaniel)

References

()

Details

Attachments

(1 file)

139.50 KB, application/msword
Details
From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 4.0) BuildID: 20020510 Reproducible: Couldn't Reproduce
Attached file BMS document
Check each existing attachment made obsolete by your new attachment. [no attachments can be made obsolete]
what an indus server ? did it ever happen again ?
->INVALID 192.168 is the reserved subnet for LANs behind a NAT router. Thus this address cannot possibly be reached by mozilla developers trying to reproduce this bug. If you have experienced this problem again using a public server, please provide the address. Thank you!
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: