no 127.0.0.1 ping!

[lbmcleod]

ok i have a computer that i want to setup on the network (WORKGROUP). i have a cable router/dhcp server (192.168.0.1) and a switch which are both working fine. The dhcp server shows the computer as 192.168.0.5. the computer connects to the internet through the LAN, and pings 192.168.0.1 but does not ping any other computer on the network and the loopback address of 127.0.0.1 also always times out. it will not connect to the workgroup through network places or anything. ive done the windows xp network setup wizard, setup the gateway as 192.168.0.1

any ideas?

thanks

 

[gunrunnerjohn]

Look at the contents of the HOSTS file located in \WINDOWS\SYSTEM32\DRIVERS\ETC. It should have a line that reads:

127.0.0.1 localhost

If not, put one in there.

 

[lbmcleod]

it was the norton internet security stopping workgroup connection - i can get into workgroup without any errors, and ping 127.0.0.1 now and ping 192.168.0.4 (another computer on network) however i cant view any workgroup computers (workgroup view is empty)

 

[lbmcleod]

duh wrong workgroup



soz for wasting neones time whos read this, on another note though, anyone got any good tutorials on how to configure norton internet security?

 

[gunrunnerjohn]

My RX for workgroup browsing issues is normally to install NETBEUI protocol all around.

 

[mboy]

Originally posted by: gunrunnerjohn
My RX for workgroup browsing issues is normally to install NETBEUI protocol all around.

No offense, but that is just a crutch. Much better off to find out why it isn't working right in the 1st place.

 

[gunrunnerjohn]

Originally posted by: mboy

Originally posted by: gunrunnerjohn My RX for workgroup browsing issues is normally to install NETBEUI protocol all around.

No offense, but that is just a crutch. Much better off to find out why it isn't working right in the 1st place.

No offence taken, but the reason I use NETBEUI is that it works. Since even Microsoft can't give a definitive answer to the question of reliable workgroup browsing, it's certainly the easy way to fix the problem.

The fragile browser election kludge that is used for workgroup browsing can be upset just by booting in a different sequence. Networks that have worked for months will suddenly not be able to find all the machines in Network Neighborhood, even though a named connection can still be made. NETBEUI solves this issue in almost all cases with no measurable downside, why not use it?

 

[mboy]

Never had any issues on my workgroup and none like that on my NT 4 domain running XP.

 

[ClearToLand]

Originally posted by: gunrunnerjohn
Look at the contents of the HOSTS file located in \WINDOWS\SYSTEM32\DRIVERS\ETC. It should have a line that reads:

127.0.0.1 localhost

If not, put one in there.

All that would have accomplished is to create a local DNS-type entry for localhost which would translate to 127.0.0.1 and still fail (if PINGing 127.0.0.1 was failing). The "usual" reason for this is some component of the TCP/IP protocol got "stepped on" and it needs to be uninstalled/re-installed.

 

[buleyb]

Originally posted by: mboy
Never had any issues on my workgroup and none like that on my NT 4 domain running XP.

Agreed, netbeui is nice for some real mismatch networks, with older clients, but I have never had an issue getting 2k/XP working in a fairly homogeneous network.

I'm sitting in a network with XP, 2k, NT, 98, Linux, Solaris, and VxWorks, running off a Samba-fied NT domain, with a bridge to NFS shares...

if this network can succeed, a few XP pro machines can get by...

 

[martind1]

Originally posted by: buleyb

Originally posted by: mboy
Never had any issues on my workgroup and none like that on my NT 4 domain running XP.

Agreed, netbeui is nice for some real mismatch networks, with older clients, but I have never had an issue getting 2k/XP working in a fairly homogeneous network.

I'm sitting in a network with XP, 2k, NT, 98, Linux, Solaris, and VxWorks, running off a Samba-fied NT domain, with a bridge to NFS shares...

if this network can succeed, a few XP pro machines can get by...

are you trying to impress us or something?

My network has all the above AND aix and hp machine. So There.

Plus I am way more handsom. You mom said so too.