NAT Slowness

Lance Reynolds

unread,

Nov 27, 2003, 9:01:25 AM11/27/03

to

Ceryx,

Sounds like it could be that your public and private nics are plugged into
the same set of hubs/switches.

--
Lance Reynolds, CNE

Craig Johnson

unread,

Nov 29, 2003, 9:52:16 PM11/29/03

to

In article <cZ4xb.10738$I04...@prv-forum2.provo.novell.com>, Cry
wrote:
> If anyone could point me in the right direction to start looking for
> problems, it'd be greatly appreciated. Thanks!
>
I wonder if this could be a virus symptom? I have seen some pretty
strange things happen to internet access with Welchia/NACHI worms
sending out traffic inside a network. Have a look at tip #73 at the
URL below.

Craig Johnson
Novell Support Connection SysOp
*** For a current patch list, tips, handy files and books on
BorderManager, go to http://www.craigjconsulting.com ***

Ceryx

unread,

Dec 1, 2003, 10:32:53 PM12/1/03

to

I've gone as far as to have the BM server plugged directly into our line
from the ISP, and had only our main file server behind the BM server,
pinging, and we still have the same problem.. Perhaps there could be some
type of virus directly on the NW file server?

Checked for both public/private interfaces plugged into the same routers, as
well as swapping every piece of cable going to the BM server. Also used
different NIC's, and even formatted/reinstalled NW+BM on the server, and
still no luck. (And I'm fairly sure it isn't our ISP's fault, since any
computer we have bypass the BM server works fine.)

I'm completely baffled. =/ It might be that I am missing some type of
setting on the BM server. I've installed all interfaces/bindings, enabled
Router mode in TCP/IP config, and turned dynamic NAT on for the public
interface.

Thank you to the people that posted ideas.

"Craig Johnson" <cra...@ix.netcom.com> wrote in message
news:VA.0000342...@ix.netcom.com...

Craig Johnson

unread,

Dec 1, 2003, 10:53:34 PM12/1/03

to

What NICs and LAN driver versions are you using?

Ceryx

unread,

Dec 2, 2003, 1:38:31 AM12/2/03

to

Oh.. Yeah. That's another thing I tried. Downloaded current versions of NIC
drivers from Intel. The server has two Intel Pro/100 S Server Adapters, and
one onboard NIC (It is a HP Netserver). One NIC is not in use, but I have
tried disabling the extra board in inetcfg and still no difference. I have
tried various combinations of the public/private IP's on the three NIC's and
still nothing.

All three were autodetected at the NW65 install. One interface has IP and
IPX bound to it (private, 10.1.1.1, netmask 255.0.0.0) and the other just
has IP (public).

I just checked another NAT related post here, though, and our file server
(not the BM server) uses a Q57 driver. Could this possibly be causing the
problem, even though computers are not actually accessing the internet
through it? All computers log in initially to the file server. Regardless, I
will update these drivers anyways.

Thanks once again

Ceryx

"Craig Johnson" <cra...@ix.netcom.com> wrote in message

news:VA.0000345...@ix.netcom.com...

Tim Heywood (NSC Sysop)

unread,

Dec 2, 2003, 6:35:33 AM12/2/03

to

The Q57is a pain or has been. Make sure that you have version 6.0x of the
Q57.LAN and it's L|DI

Also if the main file server is NW6 SP3 make sure that you have run Purge_NW and
installed tcp607k.exe

Tim

No Direct e-Mail Please!
--
****************
Tim Heywood
Independent Consultant
Scotland
(God's Country)
Novell Support Connection SYSOP
****************

In theory, practice and theory are the same,
In practice they are different!

Ceryx

unread,

Dec 2, 2003, 10:27:25 AM12/2/03

to

They're both NW65, but I will definatly try upgrading the drivers on the FS
when I get in to work this afternoon.

Thanks

Ceryx

"Tim Heywood (NSC Sysop)" <t...@iqx.co.uk> wrote in message
news:p4losvgvtgio6dqua...@4ax.com...