Problems with server connecting to workstations
We have an issue where the server can connect to the internet, however no workstations can connect to the server. it appears that the server is blocking inbound connections, however we can get a remote session via an outbound initiated connection.
We have replaced the network card, switch and cables, and still the wortstations cannot connect to the server.
no addresses are being assinged by dhcp, and static address still cannot connect. We have reisntalled DHCP to no avail.
Only error in event log relates to windows firewall service that is not running becasue of 1 network card only being used.
Pretty stuck and this is now urgent, any help would be a greatly aprreciated
We have replaced the network card, switch and cables, and still the wortstations cannot connect to the server.
no addresses are being assinged by dhcp, and static address still cannot connect. We have reisntalled DHCP to no avail.
Only error in event log relates to windows firewall service that is not running becasue of 1 network card only being used.
Pretty stuck and this is now urgent, any help would be a greatly aprreciated
David Beveridge
Can you please provide the IP address of the 1 network card in the server and the IP address of a client computer.
ASKER
Ip of server is 192.168.10.9
Client is 192.168.10.3
both class c subnets
Client is 192.168.10.3
both class c subnets
So the server can ping the default gateway
but the server can not ping the clients.
The clients can ping each other but not the server
Can the clients can ping the gateway?
but the server can not ping the clients.
The clients can ping each other but not the server
Can the clients can ping the gateway?
after you have been pinging, run try "arp -a" at a cmd prompt.
ASKER
arp command comes back with interface address - 192.168.10.5 - Mac address and then type which is dynamic. We are just testing the gateway from the clients now
ASKER
sorry internet address is 192.168.10.5, interface address is 192.168.10.9
ASKER
clients can ping gateway
if it can convert the ip address into a mac address then you have layer 2 (ethernet connectivity)
if layer 3 (ip network) doesn't work could be a firewall issue.
if layer 3 (ip network) doesn't work could be a firewall issue.
ASKER
ok, is there anyway of testing this further
If you could show us a print out of ipconfig /all from a workstation and server.
Also:
ipconfig /displaydns
route print
arp -a
It really sounds like a firewall is running on the server.
Also:
ipconfig /displaydns
route print
arp -a
It really sounds like a firewall is running on the server.
Is the switch built into your internet gateway or a separate device?
No VLANs ?
No VLANs ?
Is this 2003 SBS? If it is, try running the internet setup script again. I am guessing you have the firewall turned on because of selecting two interfaces during setup, but it isn't running because there is only one network interface up. ("connect to the internet" script) That is why you have a message in the logs about the firewall.
bevhost I think is on the right track. You have a firewall or routing and remote access setup problem. I have seen this before and it is usually in one of those two areas. Especially if you aren't getting DHCP from the server to the workstations. With this problem it is almost always one of two things: 1 Firewall, 2 IP Helper problem in a manage network switch.
If you can't find it with this, give us more details on the setup.
Server: Make/Model
OS: Version/SP level
NIC: Make/Model
Workstation: Make/Model
OS Version
NIC: Make/Model
Network Switch
Make/Model
Firewall/Router
Make/Model
Software revision
Just out of curiosity, does your router firewall also provide DHCP? If so, you need to turn it off.
Also check the status on the NIC of the server properties, advance setting tab, and see if the firewall settings button works. If it does, then your firewall/ICS is set up, if it gives you a warning about firewall/ICS not running then it is not set up.
dh
bevhost I think is on the right track. You have a firewall or routing and remote access setup problem. I have seen this before and it is usually in one of those two areas. Especially if you aren't getting DHCP from the server to the workstations. With this problem it is almost always one of two things: 1 Firewall, 2 IP Helper problem in a manage network switch.
If you can't find it with this, give us more details on the setup.
Server: Make/Model
OS: Version/SP level
NIC: Make/Model
Workstation: Make/Model
OS Version
NIC: Make/Model
Network Switch
Make/Model
Firewall/Router
Make/Model
Software revision
Just out of curiosity, does your router firewall also provide DHCP? If so, you need to turn it off.
Also check the status on the NIC of the server properties, advance setting tab, and see if the firewall settings button works. If it does, then your firewall/ICS is set up, if it gives you a warning about firewall/ICS not running then it is not set up.
dh
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.