I agree AT&T support is pretty lame and they think everyone is even lamer
than they are!

-----Original Message-----
From: Dave Parkin [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 02, 2001 10:55 AM
To: '[EMAIL PROTECTED]'
Subject: AT&T Cable Modem Problem Resolved


2 days ago I asked y'all if tomcat could be causing a problem with AT&T
Cable Modem.

I ended up throwing caution to the and listening to my internal voice.

First, I restored WinMe system to a point in time before problems began
(Nifty System Tool).

Modem connectivity began to show great promise after that, but Network
settings were not entirely correct.

Then, the Network configuration tweaking began. Bottom line rule, ignore
AT&T Phone Tech recommend (they're reading off the same sheet of paper that
they give to all of them). Here is what I recommend.

Protect yourself - Two things: 1) Ask field tech to record your assigned IP
address, Sub-net IP Address, Host, Domain Name, Gateway, DNS Server Search
Order. 2) After they install and get things running, go to your Network
configuration and record what they did to get things to run (so you can
recover later, should the need arise without relying on the Corporate Line).

After my final tweaking, I deligently recorded Network settings.  They were
not what AT&T said they should be to work.

I have not tried reinstalling and running tomcat again since - perhaps
tonight. One victory at a time!

The reason I'm documenting to tomcat mail site is this problem may have
occured after installing and starting tomcat, like it did to me. Modem
operation problem may not be related, but should it happen to you, you'll
greatly appreciate what I've docmented here vs. late night, against the
wall, head beatings accompanied by a Phone Tech telling you "everything
should work now" and rebooting 'til tomorrow).

Here we go:

Identification tab:

        Host:  XNNNNNNN-X (whatever they documented your hostname to be)

        Work group: @home

        Computer Name:  (LEAVE BLANK)


Network tab:

NIC or USB Card Properties:

        X TCP/IP (make sure it's mapped to TCP/IP)

TCP/IP Protocol Properties:

        IP Address:

        You can go 2 directions:

        * Obtain automatically

        Or the more radical

        * Specify an IP address
        (A "nice" Phone Service Tech will give you if you insist that that's
how field tech got it going.  A "not nice" Phone Service Tech will not give
you this info. - politely find an excuse to call again later - like "my wife
is calling me to dinner, gotta go, I'll tweak a little on my own and call
you back")


        WINS Config:

        * Disable


        Gateway:

        Installed gateways:

        IP Address: NNN.NNN.NNN.NNN
        Subnet Mask: 255.255.255.128
        (Service Tech will give you IP Address if you insist that that's how
tech got it going, or "let's give it a try to see if that's the problem")


        DNS Config:

        * Enable DNS

        Host: XNNNNNNN-X        Domain: cityabbrN.ST.home.com

        DNS Servier Search Order:

        NNN.NNN.NNN.NNN
        NNN.NNN.NNN.NNN
        (Service Tech will give you if you insist that that's how tech got
it going)


        Bindings:

        X Client for MS Networks (choose this option)

        NetBIOS:

        <GHOSTED>


Restart your machine and enjoy the high speed world of a AT&T Cable Modem!

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to