Networking Query Win 2k Pro, Please don't laugh at my names! 1

[RBP]

Anyone help with this one? I have a network
(want one more like!) Windows 2000 Pro, through a Linksys WAG54G RouterADSL MODEM, wireless. (Don't ask why I am not using the wireless facility Mr Rude & Sweary will call, especially if you work for Linksys)

Three pc's Tarquin, Fido, and Cedric, All have static IP's xxx,xxx,1,100, +110, +120. All set up as workgoup = develop. All files/Drives set to full share.

In network neighbourhood Tarquin can "See" Fido, but clicking on the little pc icon, brings up the following message. "Network path not found"

In network neighbourhood Fido can "See" Develop, ( the name I gave the workgoup) but when I click on the Workgroup icon I get the folloning message, "Develop not accessible The list of servers for this workgroup is currently unavailable"

In network neighbourhood, Tarquin can"See" and fully access cedric, and vice versa.
But Cedric cannot "See" Fido as an icon at all.
If this make sense, then I am not heading for the funny farm.
Can anyone help? This setup previously worked ok with a Netgear 10/100 5 port hub and 2 pc's & 100MB NIC's,

Fido is a new addition. ( I may have to put him down!)

 

[bcastner]

. Rule #1: do not assign static IPs within the default DHCP scope of the router. Try:
[tt]
Tarquin: 192.168..10
Fido: 192.168..10
Cedric: 192.168..10
[/tt] All with subnet masks of 255.255.255.0. and Gateway of 192.168.1.1

(I assume for port forwarding reasons you need static IPs).

. Rule #2: Make sure you have the basics right for Windows Networking.

Usernames with passwords. No blank or empty passwords
Same Workgroup name, unique Computer Names (less than or equal to 12 Upper Case characters), and usernames that do not match the Computer Names;

Netbios over TCP/IP enabled under Internet Properties for the LAN connection, Advanced, WINS tab. Do not use the default setting;

Something: Drive, Folder, Printer, but something shared by all machines;

Absolutely no firewall issues on the LAN side of things. Test with no firewall. Your description is perfectly apt for a fireall block on Netbios traffic on the local LAN. It should be set as a Trusted Site for traffic, without blocking of needed ports:

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q298804

An Ipconfig /all from all machines shoud report for Node Type any of the following:

Not Defined
Hybrid
Broadcast

Anything else will not work and requires a registry change and reboot:

http://support.microsoft.com/defaul...port/kb/articles/Q119/4/93.ASP&NoWebContent=1

All sharenames 12 characters in legnth and UPPER CASE.

It can take 20 or so minutes before Network Neighborhood fully reflects a rebooted machine changes following the above.

 

[RBP]

Thanks - will try your suggestions,

Not sure of the technicalities of rule #1, What value goes in the third octal of the IP in your e.g?
Can I still assign static IPs to the three pcs ( or more )? Such as 192.168.1.100,110,130? The router settings on set up were left as default. Local DHCP Server, enabled. Start ip addr 192.168.1.1 DHCP values not set (greyed out @ 0's) number of addresses 50. So DHCP Range = 192.168.1.100 - 150.

Should have stuck to netgear, nice & simple, no DHCP stuff. Need to get reading some networking principles. (can you recommend any ?)

Next quick question, Should all the PC's have uppercase names, and do the Domain names need to be u/case too?
I probably misssed all of this with the netgear stuff because it virtually set itself up.

Thank you.

 

[bcastner]

I typed the above way too quickly. Revised:
[tt]
. Rule #1: do not assign static IPs within the default DHCP scope of the router. Try:

Tarquin: 192.168.1.10
Fido: 192.168.1.11
Cedric: 192.168.1.12
All with subnet masks of 255.255.255.0. and Gateway of 192.168.1.1
[/tt]

Again, my concern is that you should not do static IPs within the DHCP scope, in your case 192.168.1.100 -- 192.168.1.149.

 

[RBP]

Thank you for your prompt reply.
I need to go and gas myself, I will be taking FIDO with me!

As you can no doubt tell, I am still confused by all of this.
Are you saying that because my Router sets the default DHCP range as 100 - 150, that I should not assign any value within this grouping to the three pc's?
If so, can you tell me, or point me in the direction of any info which will perhaps clarify the matter. I've tried reading the manual which comes with the router, and it is not terribly helpful.
In a nutshell is there anywhere I can find an explanation of DHCP, and it's uses?
In short do I ignore DHCP values, and just assign IP's to the pc's either above .149 or below .100?

Thanks again.

 

[bcastner]

Yes, that is correct.

 

[RBP]

Thank you for your kind attempts at assistance, but I have to tell you that FIDO tonight will be despatched in a sack weighted with housebricks, so that he will settle quietly on the bottom of the local canal.

I have tried all of your suggestions - and none of them have worked. I can Ping/Tracert FIDO from CEDRIC, but not vice versa. I have permitted/shared until I am blue in the face, so unless I can find a local network guru, I will retire a bad loser.

So as Client Eastwood once said "A man has to know his limitations" I am going to resort to reading some more Network guff, and using my CD burner to transfer stuff from CEDRIC to that useless mongrel FIDO. Canal permitting.

 

[bcastner]

In the end, a ping failure is either a cable/hardware issue, or an unresolved software firewall issue.

My best wishes to FIDO.

 

[patrichek]

RBP,
One thing to check first:
make sure that file and print sharing is installed in the connection properties on all pcs.

 

[arrow483]

A little network knowledge .... well, anyway

If your router has DHCP server enabled, it will assign IP addresses to anyone asking for "Automatic" IP addresses. It ignores static addresses, so if a static addresses falls into the DHCP range, you can get duplicates.

1. You should be able to turn off DHCP in the router.
2. Make sure all subnet masks are 255.255.255.0
3. Make sure the gateway addresses are the routers IP address (usually 192.168.1.1)
4. With wireless you also have a setting for access. I forget waht its called, but it defaults to "linksys". Change the name (for security). Then set this to braodcast until the PC's see it and connect, then you can turn broadcast off (for security).
5. With wireless, you also have to consider signal strength. If its marginal, funny things happen.
6. If you can't ping, you can't share. Get that working first.

 

[DanMIS]

I don't see the operating systems listed in your post, but Windows XP with Service Pack 2 installs a client firewall. That blocks ping traffic.

If you're running Windows XP then see in Windows Control panel if you have a "Windows Firewall" icon. If so, turn it off and see if you can ping both ways.

Good luck,
Dan

 

[RBP]

Thanks Dan, first ever post mentions Win2k pro, as the Op system.


STILL no further with this! which reely suxx.

Added Fido, with file sharing TCP/IP and all the restofthekak, to the network, 2* desk tops 1* laptop, all Win2k pro, Plus! a NEW laptop with XP pro NO problems adding, but Fido is doing my head in!

Can ping from Fido to Cedric, can Tracert from Fido to Cedric, but not viceyversa. Oh Dear!
Ta.

 

[NortonES2]

On each machine go to the command prompt and type:-

ipconfig /all

post the responses for the 3 PC's here.

-------------------------------

If it doesn't leak oil it must be empty!!

 

[RBP]

NortonE32.


Ipconfigs as follows 1.
C:

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : CEDRIC
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Wired Network:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NETGEAR FA311
ter
Physical Address. . . . . . . . . : 00-02-E3-16-09
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.10
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1

2. This is the troulesome one!
C:\>ipconfig/all

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : FIDO
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : SiS 900-Based PCI Fast Ethernet Adap
ter
Physical Address. . . . . . . . . : 00-0B-6A-35-A2-87
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.30
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
3. laptop

C:\>ipconfig/all

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : TARQUIN
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 3:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NETGEAR FA410TX F card
Physical Address. . . . . . . . . : 00-48-54-C0-AF-7F
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.20
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1

pc2 Fido has a network card built into the Mobo K7S8Xe asrock, others have netgear pcmcia and PCI card.
let me know if you need more.
Thanks.

 

[bcastner]

. rebuild the Winsock service stack: faq779-4625

 

[RBP]

Bcaster, this fix seems to relate to XP, will it work on win2k?
How can I tell if the service stack is jiggered?
Fido has NEVER been connected to the internet to my knowledge.
Thanks

 

[bcastner]

Works for Win2k.