Greetings!
Johnston Mark schrieb:
I have set up a PIX firewall with VPN capabilities. Everything seems
to be working except for WINS. I dont want to go through the whole
configuration, but I'm calling on anyone that has run into the same
problem or can give me any pointers.
Which WINS? I
From what i understand lmhosts is the quick and easy
way to fix the broadcast netbios problem.
NETBIOS name resolution (often confused with WINS)
is broadcast-based
--- Volker Tanger [EMAIL PROTECTED] wrote:
Greetings!
Johnston Mark schrieb:
I have set up a PIX firewall with VPN
Hi all
Can anybody give me a web site that has a decent knowledgebase on the
Cequrux firewall
Regards,
Warren van Eyssen
Systems Engineer - CNE, Citrix CCA, Compaq ASE, IBM PSS
Lan Workgroup Solutions
Tel: (021) 683-5390
Fax: (021) 683-9141
Mobile: 082-892-6960
Email: [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Cisco Security Advisory: Vulnerable SSL implementation in iCDN
Revision 1.0
For public release 2001 September 12 08:00 (GMT -0800)
Summary
A security vulnerability has been discovered in version
This is just my opinion of course but the best OS for a
roll-your-own firewall is OpenBSD. Very easy to configure and excellent documentation.
http://www.openbsd.org
-*-*-*-*-*-*-*-*-*-*-*-*-*-
All opinions are my own.
All advice is worth what you pay for it.
A little experience often upsets
On Fri, 07 Sep 2001 10:15:25 -0300, Jose Cavalcante
[EMAIL PROTECTED] said:
JC hello list
JC i Find Checkpoint Firewall-1 Admin Book in PDF
JC thanks for all
The Checkpoint CD has all of the manuals in PDF, if that's
what you are looking for.
--andrew
William--
What you've received is a probe by a machine infected with Code Red or
similar.
The fact that it's from an IP address in AOL's range is just a coincidence.
Whilst it could be one of AOL's own servers that has been infected and is
trying to spread, it more likely to be one of it's
Just thought I'd send out a message out to all you Firewalls brothers and
sisters that have been directly or indirectly affected by the horrible NYC
tragedy. My hope and prayers are out to you all.
God bless.
EK
___
Firewalls mailing list
[EMAIL
William---
Are you getting your Internet access from AOL or do you have another
Internet provide and connect to AOL through that?
I'm no expert on AOL, but my understanding is that it's dial-up access uses
it's own proprietary protocol, and it provide winsock-based IP access
through it's own
Title: WINS with PIX
WINS
is Microsoft's implementation of theNetBIOS name-server rfc. assuming your
vpn allows all netbios ports, just point all clients to your wins server.
confirm functionality by:
1.
ping by netbios name
2.
net view \\wins_server
(netbios)
if
your authenticated #2
I do not know all the details, but have you thought about using TCP
sliding windows to get your desired performance improvement? To my
knowledge, that is the more standard approach.
-Ken
At 9/11/2001 08:53 AM, liuhy wrote:
Hello
everyone,
I am on the subject that designed a
communication
AOL is configured to use a LAN(TCP/IP) connection which means its connecting
on port 5190 through our firewall and then setting up a virtual network over
that. When I get hit on port 80, I do a traceroute back to the port reported
by my intrusion detection software on my PC. That traceroute
I see 172.165.x.x addresses spoofed (probably by accident, by
people who meant to type 172.16.x.x) that if this were connectionless
traffic, I wouldn't leap to blame AOL for it. But having an
established TCP connection makes it much more likely that this really
is from them
DG
On 11
On 12 Sep 2001, at 16:00, Volker Tanger wrote:
Greetings!
Johnston Mark schrieb:
I have set up a PIX firewall with VPN capabilities. Everything seems
to be working except for WINS. I dont want to go through the whole
configuration, but I'm calling on anyone that has run into the same
On Wed, 12 Sep 2001, william.wells wrote:
[Apologies, I'm jumping into this late and responding to more than just
William's text.]
AOL hasn't gotten back to me on if this is expected behavior or not.
Since it just started, I'm inclined to believe that something is amiss
at AOL. My primary
- Original Message -
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, September 12, 2001 9:23 AM
Subject: Firewalls digest, Vol 1 #256 - 13 msgs
Send Firewalls mailing list submissions to
[EMAIL PROTECTED]
To subscribe or unsubscribe via the World Wide Web, visit
- Original Message -
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, September 12, 2001 12:02 PM
Subject: Firewalls digest, Vol 1 #257 - 6 msgs
Send Firewalls mailing list submissions to
[EMAIL PROTECTED]
To subscribe or unsubscribe via the World Wide Web, visit
Any particular reason you're sending blanks messages?
Steve Clark
Clark Systems Support, LLC
AVIEN Charter Member
www.clarksupport.com
301-610-9584 voice
240-465-0323 Efax
-Original Message-
From: Trinh Thi Kim Nhung [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September
Thank you for your answer.
I have prepared to implement the sliding windows. But considering the data
transmission is reliable in LAN compared with WAN, I want to use UDP, because it
needn't to create connection between client and server, etc. For this reason, I
have this idea that using
As you can see by your trace, running the AOL client basically creates a tunnel
between your network and the internal AOL network (which does have public addresses
but is not accessible directly from the Internet). The AOL proxy server that you
connect to, acts as a gateway, accepting internal
Hi,
I have implemented an IPSEC Tunnel between a Cisco
1750 router and a Cisco PIX 520. The tunnel is
configured to be between the inside segment(Server
LAN) of the PIX and the LAN(Client end) behind the
cisco router.
The access-list applied for the match address permits
IP access from end to
A basic doubt,Many places i have read,if a packet is fragmented to a tiny packet,
routers and many firewalls allow to pass through.My doubt is if the router or firewall
recievs a packet ,from that if it could not make out where this packet is going ,it
should drop by acess-lists or rule
22 matches
Mail list logo
