T41p & Network names

Message

huda · #1 Post by **huda** » Wed Aug 25, 2004 11:28 am

I have this weird problem with my T41p TC1GEAT:
It is not capable of resolving computers within the LAN. So instead of accessing my data with \\server\data I have to enter \\10.10.10.4\data - and thats not only at home, its also at the office, by friends and even when I go wardriving!
I updated access conntections and my WLAN drivers to the latest versions - didn't help.
The whole thing wouldnt bother me if that stupid DHCP of mine wouldnt handle my IP addresses like a roulette ball and randomly decide when to change which computers IP...

I hope there is a solution for this.... thanks

Roy_W · #2 Post by **Roy_W** » Thu Aug 26, 2004 1:25 am

huda wrote:I have this weird problem with my T41p TC1GEAT:
It is not capable of resolving computers within the LAN. So instead of accessing my data with \\server\data I have to enter \\10.10.10.4\data - and thats not only at home, its also at the office, by friends and even when I go wardriving!

This is probably a DNS issue.

1 : Which OS do you use.
2 : What is the result of doing an "ipconfig /all".
3 : Do you use a firewall.
4 : Have you made a record for your machine in yours "hosts" file.
5 : Are you using DHCP assigned or a fixed address DNS.

huda wrote: I updated access connections and my WLAN drivers to the latest versions - didn't help.

I doubt that they are the cause of the problem.

huda wrote: The whole thing wouldnt bother me if that stupid DHCP of mine wouldnt handle my IP addresses like a roulette ball and randomly decide when to change which computers IP...

This doesn't make any sense, which machine/server is responsable for DHCP, is it a computer or a router.
It would be necassary to know a little more about the DHCP ranges, the DNS allocated and the duration of a newly assigned address.

huda wrote: I hope there is a solution for this.... thanks

huda · #3 Post by **huda** » Thu Aug 26, 2004 1:45 am

1. Windows XP

2. ipconfig/all - yes, it is German

Windows-IP-Konfiguration

Hostname. . . . . . . . . . . . . : T41p
Primäres DNS-Suffix . . . . . . . :
Knotentyp . . . . . . . . . . . . : Gemischt
IP-Routing aktiviert. . . . . . . : Nein
WINS-Proxy aktiviert. . . . . . . : Nein

Ethernetadapter Drahtlose Netzwerkverbindung 2:

Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : 11a/b/g Wireless LAN Mini PCI Adapte
r
Physikalische Adresse . . . . . . : 00-05-4E-45-7F-21
DHCP aktiviert. . . . . . . . . . : Ja
Autokonfiguration aktiviert . . . : Ja
IP-Adresse. . . . . . . . . . . . : 10.10.10.3
Subnetzmaske. . . . . . . . . . . : 255.255.255.0
Standardgateway . . . . . . . . . : 10.10.10.1
DHCP-Server . . . . . . . . . . . : 10.10.10.1
DNS-Server. . . . . . . . . . . . : 10.10.10.1
Lease erhalten. . . . . . . . . . : Donnerstag, 26. August 2004 04:11:00

Lease läuft ab. . . . . . . . . . : Freitag, 27. August 2004 04:11:00

Ethernetadapter LAN:

Medienstatus. . . . . . . . . . . : Es besteht keine Verbindung
Beschreibung. . . . . . . . . . . : Intel(R) PRO/1000 MT Mobile Connecti
on
Physikalische Adresse . . . . . . : 00-0D-60-B0-38-96

Ethernetadapter BT LAN:

Medienstatus. . . . . . . . . . . : Es besteht keine Verbindung
Beschreibung. . . . . . . . . . . : Bluetooth LAN Access Server Driver #
2
Physikalische Adresse . . . . . . : 00-20-E0-74-5D-12

Ethernetadapter BT:

Medienstatus. . . . . . . . . . . : Es besteht keine Verbindung
Beschreibung. . . . . . . . . . . : Bluetooth LAN Access Server Driver
Physikalische Adresse . . . . . . : 00-20-E0-74-5D-12

3. Firewall
Yes, I use the firewall that is built in the Netgear Router WGT624 which is also WAN router and DHCP

4. record
No and I have no idea what you are talking about

5. DHCP
Everythings being assigned from DHCP.

I dont think the problem is the router as all of my notebooks (T40, T41p, T41, T42p and X40) have no problems there....

Roy_W · #4 Post by **Roy_W** » Thu Aug 26, 2004 3:55 am

1 : What happens when you "ping server".
2 : Do the following

Note your IpAdress somewhere :
"ipconfig /release"
"ipconfig /renew"
"ipconfig /all"

Normally the DHCP serve will renew your lease and "Normally" will return you the same IpAddress as long as your Mac Address hasn't change.

3 : Something a little strange, You are using IpAdresses that are normally used on Class A Networks but with a Class C Subnet masK. It shouldn't cause any problems it just a little unusual to see "10.x.x.x" with "255.255.255.0"

huda · #5 Post by **huda** » Thu Aug 26, 2004 6:17 am

1: That happens
C:\Dokumente und Einstellungen\huda>ping s02
Ping-Anforderung konnte Host "s02" nicht finden. Überprüfen Sie den Namen, und versuchen Sie es erneut.

meaning Host s02 not found...

2: I tried that before

3: Thats just an old habit from the network I had 8 years ago.

Roy_W · #6 Post by **Roy_W** » Thu Aug 26, 2004 8:58 am

huda wrote:1. Windows XP

2. ipconfig/all - yes, it is German
Windows-IP-Konfiguration

Hostname. . . . . . . . . . . . . : T41p
Primäres DNS-Suffix . . . . . . . :
Knotentyp . . . . . . . . . . . . : Gemischt
IP-Routing aktiviert. . . . . . . : Nein
WINS-Proxy aktiviert. . . . . . . : Nein

....

Huda,

From this listing your machines appears to be called "T41p" and not "SO2" or "Server".

Can you "ping T41p"

huda · #7 Post by **huda** » Thu Aug 26, 2004 9:12 am

ah sorry... heres the right one and it works.

Ping T41p [10.10.10.3] mit 32 Bytes Daten:

Antwort von 10.10.10.3: Bytes=32 Zeit<1ms TTL=128
Antwort von 10.10.10.3: Bytes=32 Zeit<1ms TTL=128
Antwort von 10.10.10.3: Bytes=32 Zeit<1ms TTL=128
Antwort von 10.10.10.3: Bytes=32 Zeit<1ms TTL=128

Ping-Statistik für 10.10.10.3:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0 (0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 0ms, Maximum = 0ms, Mittelwert = 0ms

Roy_W · #8 Post by **Roy_W** » Thu Aug 26, 2004 9:36 am

Huda,

So now you can access your machine with \\T41p\Data.

huda · #9 Post by **huda** » Thu Aug 26, 2004 9:46 am

I can access my machine from my machine, but I cannot access any other computer by name.

T41p can access \\T41P\XXX

Server cannot access \\T41P\XXX, only \\10.10.10.3\XXX

T41p cannot access \\SERVER\DATA, only \\10.10.10.10\DATA

ZPrime · #10 Post by **ZPrime** » Thu Aug 26, 2004 11:25 am

what is your "netbios over TCPIP" setting under TCP/IP properties for that connection?

if netbios is off, you won't be able to go by name unless you have a real DNS server (that is doing dynamic updates to DNS for DHCP clients).

Roy_W · #11 Post by **Roy_W** » Thu Aug 26, 2004 11:48 am

Huda,

Can you supply the results from

"netstat -an"

huda · #12 Post by **huda** » Thu Aug 26, 2004 11:56 am

hope this helps...

ABHÖREN = LISTENING
HERGESTELLT = ESTABLISHED
FIN_WARTEN = FIN_WATING
WARTEND = WAITING
SYN_GESENDENT = SYN_SENT

Aktive Verbindungen

Proto Lokale Adresse Remoteadresse Status
TCP 0.0.0.0:135 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:445 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:1025 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:1029 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:3226 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:3389 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:3500 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:3571 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:4067 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:4165 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:4168 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:4169 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:4222 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:4229 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:4243 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:4366 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:4377 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:4464 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:4466 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:4558 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:4563 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:4566 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:4571 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:4576 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:4577 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:4582 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:4583 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:4584 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:4585 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:4586 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:4587 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:4588 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:5000 0.0.0.0:0 ABHÖREN
TCP 0.0.0.0:13796 0.0.0.0:0 ABHÖREN
TCP 10.10.10.3:139 0.0.0.0:0 ABHÖREN
TCP 10.10.10.3:3124 0.0.0.0:0 ABHÖREN
TCP 10.10.10.3:3500 213.37.10.149:2383 HERGESTELLT
TCP 10.10.10.3:4067 80.143.168.245:2859 HERGESTELLT
TCP 10.10.10.3:4168 205.188.248.199:20480 HERGESTELLT
TCP 10.10.10.3:4169 205.188.248.199:20480 HERGESTELLT
TCP 10.10.10.3:4229 207.46.106.103:1863 HERGESTELLT
TCP 10.10.10.3:4243 217.83.46.248:1475 HERGESTELLT
TCP 10.10.10.3:4366 64.14.61.67:1329 FIN_WARTEN_1
TCP 10.10.10.3:4377 64.14.61.68:2561 FIN_WARTEN_2
TCP 10.10.10.3:4399 62.99.135.114:110 WARTEND
TCP 10.10.10.3:4400 213.239.194.67:110 WARTEND
TCP 10.10.10.3:4401 213.46.255.2:110 WARTEND
TCP 10.10.10.3:4402 217.172.163.8:110 WARTEND
TCP 10.10.10.3:4403 66.235.219.118:110 WARTEND
TCP 10.10.10.3:4404 62.99.135.114:110 WARTEND
TCP 10.10.10.3:4405 217.172.163.8:110 WARTEND
TCP 10.10.10.3:4406 217.172.163.8:110 WARTEND
TCP 10.10.10.3:4407 213.239.194.67:110 WARTEND
TCP 10.10.10.3:4409 64.14.61.81:1397 WARTEND
TCP 10.10.10.3:4411 64.14.61.80:1937 WARTEND
TCP 10.10.10.3:4414 64.14.61.72:1865 WARTEND
TCP 10.10.10.3:4415 64.14.61.68:1680 WARTEND
TCP 10.10.10.3:4421 64.14.61.76:1974 WARTEND
TCP 10.10.10.3:4432 64.14.61.71:1967 WARTEND
TCP 10.10.10.3:4436 64.14.61.73:1414 WARTEND
TCP 10.10.10.3:4448 64.14.61.72:1915 WARTEND
TCP 10.10.10.3:4457 80.218.125.113:2281 WARTEND
TCP 10.10.10.3:4458 64.14.61.72:1359 WARTEND
TCP 10.10.10.3:4460 64.14.61.68:2071 WARTEND
TCP 10.10.10.3:4461 64.14.61.67:1321 WARTEND
TCP 10.10.10.3:4463 64.14.61.67:1336 WARTEND
TCP 10.10.10.3:4464 64.14.61.68:1216 FIN_WARTEN_2
TCP 10.10.10.3:4466 213.135.234.165:3863 HERGESTELLT
TCP 10.10.10.3:4476 64.14.61.71:1804 WARTEND
TCP 10.10.10.3:4477 64.14.61.68:1667 WARTEND
TCP 10.10.10.3:4482 64.14.61.67:2083 WARTEND
TCP 10.10.10.3:4483 64.14.61.71:2391 WARTEND
TCP 10.10.10.3:4492 64.14.61.81:1459 WARTEND
TCP 10.10.10.3:4493 64.14.61.71:2492 WARTEND
TCP 10.10.10.3:4494 64.14.61.67:1674 WARTEND
TCP 10.10.10.3:4499 64.14.61.72:1650 WARTEND
TCP 10.10.10.3:4501 64.14.61.67:2562 WARTEND
TCP 10.10.10.3:4504 64.14.61.72:1734 WARTEND
TCP 10.10.10.3:4508 64.14.61.73:1785 WARTEND
TCP 10.10.10.3:4518 80.218.125.113:2281 WARTEND
TCP 10.10.10.3:4521 64.14.61.72:2198 WARTEND
TCP 10.10.10.3:4522 64.14.61.73:1818 WARTEND
TCP 10.10.10.3:4524 62.99.135.114:110 WARTEND
TCP 10.10.10.3:4525 213.239.194.67:110 WARTEND
TCP 10.10.10.3:4526 213.46.255.2:110 WARTEND
TCP 10.10.10.3:4527 217.172.163.8:110 WARTEND
TCP 10.10.10.3:4528 66.235.219.118:110 WARTEND
TCP 10.10.10.3:4529 217.172.163.8:110 WARTEND
TCP 10.10.10.3:4530 213.239.194.67:110 WARTEND
TCP 10.10.10.3:4531 62.99.135.114:110 WARTEND
TCP 10.10.10.3:4532 217.172.163.8:110 WARTEND
TCP 10.10.10.3:4533 64.14.61.68:2007 WARTEND
TCP 10.10.10.3:4537 64.14.61.72:1373 WARTEND
TCP 10.10.10.3:4540 64.14.61.71:1926 WARTEND
TCP 10.10.10.3:4544 64.14.61.73:2706 WARTEND
TCP 10.10.10.3:4546 0.0.0.0:0 ABHÖREN
TCP 10.10.10.3:4550 64.14.61.76:2043 WARTEND
TCP 10.10.10.3:4551 64.14.61.81:1500 WARTEND
TCP 10.10.10.3:4558 216.229.83.237:80 HERGESTELLT
TCP 10.10.10.3:4560 64.14.61.67:1782 WARTEND
TCP 10.10.10.3:4563 216.229.83.237:80 HERGESTELLT
TCP 10.10.10.3:4566 64.14.61.67:2385 HERGESTELLT
TCP 10.10.10.3:4568 64.14.61.81:1640 WARTEND
TCP 10.10.10.3:4569 64.14.61.72:2459 WARTEND
TCP 10.10.10.3:4571 64.14.61.74:2241 HERGESTELLT
TCP 10.10.10.3:4576 64.14.61.72:2264 HERGESTELLT
TCP 10.10.10.3:4577 64.14.61.70:1737 SYN_GESENDET
TCP 10.10.10.3:4581 64.14.61.74:2535 WARTEND
TCP 10.10.10.3:4582 64.14.61.77:2641 SYN_GESENDET
TCP 10.10.10.3:4583 64.14.61.77:1450 SYN_GESENDET
TCP 10.10.10.3:4584 64.14.61.67:1370 HERGESTELLT
TCP 10.10.10.3:4585 64.14.61.70:2647 SYN_GESENDET
TCP 10.10.10.3:4586 64.14.61.73:2584 HERGESTELLT
TCP 10.10.10.3:4587 64.14.61.72:1300 HERGESTELLT
TCP 10.10.10.3:4588 64.14.61.66:1758 SYN_GESENDET
TCP 127.0.0.1:3002 0.0.0.0:0 ABHÖREN
TCP 127.0.0.1:3003 0.0.0.0:0 ABHÖREN
TCP 127.0.0.1:3004 0.0.0.0:0 ABHÖREN
TCP 127.0.0.1:5180 0.0.0.0:0 ABHÖREN
UDP 0.0.0.0:445 *:*
UDP 0.0.0.0:500 *:*
UDP 0.0.0.0:3014 *:*
UDP 0.0.0.0:3105 *:*
UDP 0.0.0.0:3571 *:*
UDP 0.0.0.0:4238 *:*
UDP 0.0.0.0:4755 *:*
UDP 0.0.0.0:4756 *:*
UDP 0.0.0.0:4757 *:*
UDP 10.10.10.3:9 *:*
UDP 10.10.10.3:123 *:*
UDP 10.10.10.3:137 *:*
UDP 10.10.10.3:138 *:*
UDP 10.10.10.3:1900 *:*
UDP 10.10.10.3:20394 *:*
UDP 127.0.0.1:123 *:*
UDP 127.0.0.1:1900 *:*
UDP 127.0.0.1:3013 *:*
UDP 127.0.0.1:3029 *:*
UDP 127.0.0.1:3264 *:*
UDP 127.0.0.1:4188 *:*
UDP 127.0.0.1:4342 *:*
UDP 127.0.0.1:4774 *:*

huda · #13 Post by **huda** » Thu Aug 26, 2004 12:09 pm

Under TCP/IP / WINS
NetBios in TCP/IP is set to "Standard". This option says that if the DHCP does not offer NetBios, it will activate NetBIOS over TCP/IP.

There is also two more options to Activate and to Deactrive NetBIOS. I tried both, no joy there..

There is also a checkbox for LMHOSTS, its not checked. I tried with and without LMHOSTS, no difference.

Roy_W · #14 Post by **Roy_W** » Thu Aug 26, 2004 12:20 pm

Huda,

Ok Netbios is obviously running and listening , port 139.

Can you do the following

1 : net view Server
2 : net view SO2

(Normally you should see something like the following

Share name Type Used as Commen

-----------------------------------
C Disk
D Disk
DESKTOP Disk
****** Disk
Shared ****** Disk (UNC)
SharedDocs Disk
The command completed successfully.

/**********************************************
if these commands fail try doing the same thing but replace the names with their respective IPaddress.

If neither works try the following and retry

Check to see whether NetBIOS settings are taken from the DHCP server, or whether NetBIOS is enabled or disabled. If you are using DHCP for this host computer, select Use NetBIOS setting from the DHCP server. Otherwise, select enable NetBIOS over TCP/IP.

Roy_W · #15 Post by **Roy_W** » Thu Aug 26, 2004 12:29 pm

Huda,

Does the problem only exist with the Wlan connection or does it also exist with the RJ45 Cabled connection.

Can you "telnet T41P 139" from the Server or from SO2, if the telnet is successful you should see nothing but a blank screen otherwise yill get a failure message of some kind.

huda · #16 Post by **huda** » Sat Aug 28, 2004 7:50 am

The Problem occurs with Wlan and RJ45 connected.
And telnet t41p 139 wont connect...

net view s02 gives me System error 53 - Networkpath not found.
same with any other target in the network..

What can this be? I'm using a standard Preload, standard network settings, no firewall or anything installed in the TP, its just a normal XP installation!

huda · #17 Post by **huda** » Mon Aug 30, 2004 2:48 am

Help.. anybody?

T41p & Network names

T41p & Network names

Re: T41p & Network names

Who is online