PDA

View Full Version : Network Probs...



Spermy
27-12-04, 14:54
I have a wee bit of a problem.

I'm on a network - 1 gateway host - and 2 clients.

all connected via a hub.

The host has a USb connectiuon to the dsl modem type thingymabob. *technical!!!*, and also a A connection to the hub.

The client computers are plugged straight into the hub. Now the tricky bit is - I can access the net on the host, and on one client. But I can't get onto the net on my other client. I could last night, and nothing has changed since, it's just kaput.

If rerun the wizard. Setup all my firewallyness, even tried it with the firewall off, no joy. Kind of at a loss for what to do next. :confused: :confused:

Any takers? Cos I'm sure a few people ingame would love to give me a built in air vent for my head as a birthday pressie :p

Lexxuk
27-12-04, 15:14
go into DOS, type ipconfig and make sure the IP addy is the same as ur networks, i.e. 192.168.1.* if its 169. or something, means its not being assigned an IP address, so go into network settings, click tcp/ip thingy, then instead of get IP, put in ur own, like 192.168.1.55

/edit - default gateway should be the ip of the puter connected to the net, usually 192.168.1.1

Reefer
27-12-04, 15:58
First of all I would leave out the wizard all together and configure the clients manually :cool:

If you have DHCP enabled you can jsut try enabling and disabling your network connection to have DHCP configure it again. (you might have duplicate IP for some reason)

Also check that your clients both have the DNS servers of your ISP configured and that the gateway is set to your server's IP.

Enable the automaticaly detect internet explorer settings (unless your isp uses a specialised configuration script) and make sure that your internet proxy is disabled on the client. Also disable your proxy on the server for testing pruposses.

Disable the windows firewall and use a third party (free or not to be) firewall to specify your internal network range and/or set it to allow incomming and outgoing trafic on your clients specific MAC adress (found by typing ipconfig /all in your clients dosbox).

if it still doesn't work test the following.

- ping to your server from both clients
- ping to the DNS of your ISP from both clients
- ping a random website/ ip adress on the internet
- perform a tracert to a random site's IP to see where it gets blocked.


Things you should know when using DHCP (automatically assigns ip adresses)

- booting a clients before the server finished booting -> client doesn't get configured -> solve by enabling/disabling your clients connection or use ipconfig /release ...ipconfig /renew in a dos box on the client
- 2 clients booting at the same time, usually they recieve IP adresses in turn but in rare occasions a duplicate adress might be handed out -> "renew" ip adress on your client
- more then one DHCP services are running on the network -> clients can't communicate with each other and/or certain server



There I hope this mumbojumbo was a bit helpfull :angel:

Spermy
27-12-04, 16:07
First of all I would leave out the wizard all together and configure the clients manually :cool:

If you have DHCP enabled you can jsut try enabling and disabling your network connection to have DHCP configure it again. (you might have duplicate IP for some reason)

Also check that your clients both have the DNS servers of your ISP configured and that the gateway is set to your server's IP.

Enable the automaticaly detect internet explorer settings (unless your isp uses a specialised configuration script) and make sure that your internet proxy is disabled on the client. Also disable your proxy on the server for testing pruposses.

Disable the windows firewall and use a third party (free or not to be) firewall to specify your internal network range and/or set it to allow incomming and outgoing trafic on your clients specific MAC adress (found by typing ipconfig /all in your clients dosbox).

if it still doesn't work test the following.

- ping to your server from both clients
- ping to the DNS of your ISP from both clients
- ping a random website/ ip adress on the internet
- perform a tracert to a random site's IP to see where it gets blocked.


Things you should know when using DHCP (automatically assigns ip adresses)

- booting a clients before the server finished booting -> client doesn't get configured -> solve by enabling/disabling your clients connection or use ipconfig /release ...ipconfig /renew in a dos box on the client
- 2 clients booting at the same time, usually they recieve IP adresses in turn but in rare occasions a duplicate adress might be handed out -> "renew" ip adress on your client
- more then one DHCP services are running on the network -> clients can't communicate with each other and/or certain server



There I hope this mumbojumbo was a bit helpfull :angel:

Done, done and done :p

This baffleses me completely - It appears it's the permissions on the host thats causing the probs.

I should be ashamed! We cover networking on my course, and I'm bloody clueless!

Xeno LARD
27-12-04, 16:12
Basically.

IP needs to be different on each of the pc's.
Subnet Mask need to be the same on all of the pc's.

From the machine that doesn't work: Ping the gateway, if you get a reply; do a small dance.

If no reply make sure you're using a patch cable and not a x-over, that won't work :(.

Now, if you can ping the gateway try pinging google.com, if there's no reply, try pinging 216.239.57.99, this is the IP of the google servers. If you can ping that but not google.com then it's your DNS that isn't working. Try setting your DNS to 194.74.65.69 and 194.72.9.38. These are the BT DNS servers.

If still not working then cry yourself to sleep tonight or paypal me enough for a train ticket to your house, i've always wanted to meet a intraweb person.

Spermy
27-12-04, 17:01
Basically.

IP needs to be different on each of the pc's.
Subnet Mask need to be the same on all of the pc's.

From the machine that doesn't work: Ping the gateway, if you get a reply; do a small dance.

If no reply make sure you're using a patch cable and not a x-over, that won't work :(.

Now, if you can ping the gateway try pinging google.com, if there's no reply, try pinging 216.239.57.99, this is the IP of the google servers. If you can ping that but not google.com then it's your DNS that isn't working. Try setting your DNS to 194.74.65.69 and 194.72.9.38. These are the BT DNS servers.

If still not working then cry yourself to sleep tonight or paypal me enough for a train ticket to your house, i've always wanted to meet a intraweb person.

:lol:

A very strange one this was, allsorts of things that were fine yesterday were screwed today.

Very strange, but I sense someone must have been having a laugh =/


Close Please :)