Are you sure it's RENEWING it's IP and not just working from an existing
lease? Your below symptoms seem to indicate a physical problem - cable,
switch port, etc. Also try hard coding speed/duples settings rather than
autodetect.
It should always be able to resolve it's own name BTW ...
-----Original Message-----
From: Greg Page [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 06, 2001 4:08 PM
To: NT System Admin Issues
Subject: RE: Strange TCP/IP issue
Loopback - yes
IP address - yes
Router - no
Itself by name - no way to resolve it's own name
DNS by IP and name - no and no
It does get an IP from DHCP and the IP and Mac address are in arp cache.
Greg
-----Original Message-----
From: Webb, Brian (Telecom) [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 06, 2001 2:38 PM
To: NT System Admin Issues
Subject: RE: Strange TCP/IP issue
Can you ping Loopback (127.0.0.1)?
Can it ping itself by number?
Can it ping the router by number?
Can it ping itself by name?
Can it ping your DNS server by number?
Can it ping your DNS server by name?
Somewhere in that string of pings you should be able figure out where the
problem is.
Disclaimer: This is the current user's personal opinion and is not made on
behalf of my employer.
-----Original Message-----
From: Greg Page [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 06, 2001 1:32 PM
To: NT System Admin Issues
Subject: RE: Strange TCP/IP issue
That didn't show any conflicts.
Greg
-----Original Message-----
From: Peter Pearson [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 06, 2001 2:21 PM
To: NT System Admin Issues
Subject: Re: Strange TCP/IP issue
try using NBTSTAT -n (at a dos prompt) to see if there are any conflicts.
----- Original Message -----
From: Greg Page <mailto:[EMAIL PROTECTED]>
To: NT System Admin <mailto:[EMAIL PROTECTED]> Issues
Sent: Thursday, September 06, 2001 2:14 PM
Subject: Strange TCP/IP issue
I have a strange TCP/IP issue that came up this morning and is still
unresolved. A use could no longer communicate with any domain resources on
his laptop. The computer got an IP from the DHCP server but that was it. No
mapping drives, no network login, no pinging. It could resolve names from
it's lmhosts file and the IP and MAC address would show up in the arp cache.
I uninstalled and reinstalled the NIC and TCP protocol a couple times and it
couldn't fix the problem.
Anyone have any ideas?
Greg
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
